John Funk Community Champion

Hi SuJeong - Welcome to the Atlassian Community! Are there Components in the issue? Also, did you look at the History of the issue to see who/what might have assigned it to you?

Thanks @Mel Policicchio !! When are you bringing data residency to the Middle East? Specifically, UAE or Saudi Arabia?

Thanks @Andy Heinzer !!

Try adding a Log action for the value of that field after the second condition. 

Okay thanks. Try this. Add a Condition after the initial trigger for Issue Type = Task Add a Condition after the Branch for Related Issues condition. Select Linked Issues for the Related Issues. Then for the Condition choose All match specified JQL. For Matching JQL use statusCategory = Done Remove your current Condition…

Can you share your workflow? And can you answer my questions above?

Go to Settings > Issues > Issue Type Hierarchy But I don't think you will find set up will support what you are trying to do. You are trying to make a service-request issue the parent of a task issue. You probably should not populate the Parent field on the create - get rid of that field. Then after your create action, add…

Hmmm, okay, let me see if someone from Atlassian can check on you here.

That's just your scheme. We need the hierarchy. Go to Settings > Issues > Issue Type Hierarchy. 

It would be trigger issue if you want it to be the same as the one that originally got assigned and caused the rule to fire. 

I am not a water person at all. Give me the mountains and a cabin. Or I guess the desert. :-)

Hi @Сергей Асмоловский - Welcome to the Atlassian Community! That is very strange behavior. What type of board is it? Scrum or Kanban? Try to click on the Edit Filter Query link. Then if it still has numbers for the project, change it back to HRM. 

Hi Ori, Can you share with us the two rules you have created already? If you have not created yet, give it a shot first and then post them here. 

Hi Mohamed - Welcome to the Atlassian Community! Can you please share a screenshot of your rule? 

Thanks. What issue type is the issue being created? And what is your Issue Type Hierarchy?

No, I am talking about this same screen. When does this screen get shown? When you are trying to have the issue to Done? That's the same transition that you need to add the Field Required validator. 

Thank you for that. Can you now show us the details of the Create Issue action?

Hi Amvrosios - Welcome to the Atlassian Community! Just try this: project = "Customer service desk" and assignee = XXXXXXX AND statusCategory != Done

Hi Raju I don't think I completely follow you. Is this the scenario? Someone tries creates an issue with a type of Task. And if they select Low for the Priority field value, it will not let them create the issue, but gives them an error message that the Priority must be higher in order to create the issue. Is that correct?

You are welcome. 

Hi Sefa, On the same transition that uses the screen above, add a Validator for Field Required. Then select the field. Save the workflow and publish it. 

Hi Mark - Welcome to the Atlassian Community! Is there a reason you are using JSON instead of just an Edit Issue action and selecting the field? Also, what type of field is it? Does the field have any restrictions based on Context? 

Great! Glad you got a solution for it. 

So, if it is the parent level field value that is changing, and you want to copy that down, then you will need to add a Branch for Children between the two Conditions. And move the second Condition and subsequent field update under the branch. 

Hi Shivani, Can you share the rule that you have so far (a screenshot please)? And what is not working with it. 

Hi John, Yes, you should open a support ticket with Atlassian and have them check the suppression list for that email address. https://support.atlassian.com/contact/#/

Hi Nic - Welcome to the Atlassian Community! You should open a support ticket with Atlassian and have them check the suppression list for that email address. https://support.atlassian.com/contact/#/

Hi Ytsen, Can you share the Issue Type Hierarchy for your site? 

Hi Dzulfikar - Welcome to the Atlassian Community! You should open a support ticket with Atlassian to see if the email address has been put on their suppression list. https://support.atlassian.com/contact/#/

Hi @sh.cho - Welcome to the Atlassian Community! Can you please share a screenshot of the actual rule?