Project Syncs - Azure DevOps - "Status" field Mapping Bug Workaround

For mapping ADO State to Wrike Status, we experienced a bug  wherein the cursor could not access the trash icon to the right of the ADO State name, thereby preventing removal of ADO states from the mapping. This may be due to the length of text in the ADO State field (see attached).

Workaround: Perform multiple zoom ins (CNTL +) in the browser window to be able to get the cursor to touch the trash bucket icon -  

MORE DETAIL: When we first added the mapping "Status" to "State", Wrike popped up a message to 'give it a few moments' while it performed its own (initial/automated) mapping; this generally aligned with Wrike's 4 overall Workflow types of Active, Completed, Deferred and Cancelled.  The result was a block of ADO statuses mapped to a block of Wrike workflows, for example, anything it considered similar to Active, which includes Wrike workflows such as New, In Progress, In Testing and more, were mapped to a block of ADO statuses such as New, In Progress, In Testing, Waiting on Dev, etc. 

We wanted to disambiguate these, so we needed to remove items from the automatic groupings and make them more one-to-one: the goal being "New" maps to "New", and "In Progress" maps to "In Progress", etc.  (We recognize that ADO might have multiple states of In Progress, so we would select all of those.)

Upvote 0
👍 Spot On 💡 Innovative Approach 💪 Stellar Advice ✅ Solved 🪄 Remove Kudos
1 Kommentar
Avatar
Cansu

Hi Mike Murray, welcome to the Community and thank you for taking the time to share your tips and advice here!

0
👍 Spot On 💡 Innovative Approach 💪 Stellar Advice ✅ Solved 🪄 Remove Kudos

Folllowing List for Post: Project Syncs - Azure DevOps - "Status" field Mapping Bug Workaround
[this list is visible for admins and agents only]

Nach oben
Didn’t find what you were looking for? Write new post