Unanswered

Azure devops work item how to create a unassigned issue

(0) Share

Report

Posted on by hashik4d

I am trying to automate when a email arrives to a mailbox folder create a azure work using and leave it unassigned for someone to pick it. Even if the "Assigned To" field is empty it was assigning to me. I tried null "uassigned" but the flow fails.

Categories:

Using flows

I have the same question (0)

All responses (6)

Answers (1)

Expiscornovus 33,189 Most Valuable Professional on at

Like (0)

Report

Hi @hashik4d,

Did you add null as an expression?

Was this reply helpful? Yes No
hashik4d 11 on at

Like (0)

Report

HI @Expiscornovus ,

I just tired and it still assigns ticket in my name,

Was this reply helpful? Yes No
Expiscornovus 33,189 Most Valuable Professional on at

Like (0)

Report

Hi @hashik4d,

Which process are you using (Agile, Scrum) in you project?

And just to double check, you haven't got a custom rule for this in your process? See an example of such a rule below.

https://learn.microsoft.com/en-us/azure/devops/organizations/settings/work/custom-rules?view=azure-devops

I tested the null expression with the out-of-the-box Scrum process and a bug work item. My test result can be seen below:

Was this reply helpful? Yes No
hashik4d 11 on at

Like (0)

Report

Hi @Expiscornovus ,

I checked and there is no rules at the org level. we are using agile and one thing i noticed is its only happening for "Issues" but the other other items like bug, tasks are creating as "unassigned". Will use the other items, it doesn't matter what we use as long as the mails are created in ADO. Big Thanks for you time and effort on this.

Was this reply helpful? Yes No
Verified answer

Expiscornovus 33,189 Most Valuable Professional on at

Like (2)

Report

Hi @hashik4d,

I think that is embedded into the Issue work item type of the Agile process. When I create a new issue work item via the interface within one of my test Projects which uses the Agile process the same thing happens.

So, it is not your flow causing this 😁

You can probably create an inherited process and apply a rule to change this behaviour for issue work item types as well in ADO 😄

Was this reply helpful? Yes No
bishah 3 on at

Like (0)

Report

Thank you for an easy solution. I have been facing this issue for quite a long time.

Was this reply helpful? Yes No