Productivity Tools

Tools written by an IT business manager, a passionate developer.

EcoVadis AzureDevOps

Module is written to help manage tasks on the AzureDevOps. It is module dedicated for my team at EcoVadis.

Setup MasterConfiguration

Install-Module -Name ProductivityTools.PSMasterConfiguration
Set-MasterConfiguration

Check if in the path c:\Users\pwujczyk\Documents\ProductivityTools.MasterConfiguration\ you have json file

MasterConfiguration

Setup AzureDevops

Install-Module -Name EcoVadis.AzureDevOps   
{     "TTTFSAddress":"https://azuredevops.ecovadis.com/EcoVadisApp_TeamProjectCollection/",     "TTpat":"ti45xwu6mmeakxrcdmdpg7kadefdsk6gc4sxa",     "TTuserName":"Pawel Wujczyk <PRD\\pwujczyk>", }
MasterConfiguration

Use it.

New-FEStealing "StealingFE" 13 New-BEStealing "StealingBE" 14 Get-TFSItem 101856
Stealing

Move-ItemsToSprint – from stack rank

Moving all users stories which will greater or equal 99999999

Move-ItemsToSprint -TargetSprint 64 -FromStackRank 99999999 -Verbose

Move-ItemsToSprint – not closed

Moving all users stories which are in the status Dev Active,L2 Approved, move all tasks and eco Bugs which are in the status New, Active, Code Review, to given sprint.

Move-ItemsToSprint -NotClosed -TargetSprint 68 -Verbose

Statuses of US which will be moved: – Dev Active – L2 Approved

Statuses of tasks and bugs which will be moved: – New – Active – Code Review – L2 Approved

Statuses of the tasks and bugs which will be cloned – Active – Code Review

Calculate Sprint hours

Get-CurrentBacklogEstimation

Set-IsPlanned

Command sets IsPlanned flag to all tasks in given query.

Set-IsPlanned  Set-IsPlanned -Value $true

Add-ProgressiveRollout

Add-FEProgressiveRollout 113937 Add-FEProgressiveRollout 113937 -Silent

If the task already exist cmdlet will throw exception, unless you will use -Silent switch.

Add-Testing

It creates two items: Test Case and Testing task for given US.

Add-Testing113937 Add-Testing 113937 -Silent

If the task already exist cmdlet will throw exception, unless you will use -Silent switch.

Add-FTRemoval

Optimizely json structure

rollouts featureFlags audiencies

To check if given feature flag has audience we need to take value from featureFlags node

{ "experimentIds": [], "rolloutId": "19580570502", "variables": [], "id": "19581921496", "key": "angry_nerds_audience_test" }

Find rollout using rolloutId

{ "experiments": [ { "   status": "Running",     "audienceConditions": [     "or",     "19320882195"     ],     "audienceIds": [     "19320882195"     ],     ... "id": "19580570502" },

Check if audienceIds are not empty.

It takes all US from current sprint. It checks if already we have removal FT US and if not creates two of them: – technical one to remove it from code – business one to archive it in optimizely