You’re offline. This is a read only version of the page.
11
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.
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 😄
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.
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.
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:
#1
WarrenBelz
146,651
Most Valuable Professional
#2
RandyHayes
76,287
Super User 2024 Season 1
#3
Pstork1
65,999
Most Valuable Professional
Share
Report
All responses (
Answers (
