John Funk Community Champion

Hi Simon, You are not really going to be able to control that outside of setting a value of a hidden field in the first rule, and then have the second rule fire based on the value of the hidden field changing. And so on. 

And there is nothing in the history for the issue when you modify the timeline view?

I am confused again - you never mentioned the Assignee being unassigned. What are the EXACT requirements for what you are trying to accomplish? 

What kind of project are you using? Team-managed? Company-managed? Jira Software? Jira Work Management? 

I don’t understand - what’s the purpose of having an assignee for the Epic if it’s constantly changing?

Okay, that's just the Default Issue Screen. If you change it, it will affect all issues on that project, but that's it. 

Hi @Ananthakumaran Why are you using the Advanced JSON format not just selecting the field? 

Hi Bogdan - Welcome to the Atlassian Community! Try just: {{issue.Business Value}} / {{issue.Time Estimate}}

The Conditions in the Workflow will not keep users from updating fields - it will only control who can transition the issue to another step in the workflow. 

Hi @坂下弥 Can you share a screenshot of what you are calling the Assignment layout? 

Hi Vishnu, It doesn't make sense to update the Epic assignee based on one of the child assignees. You might have multiple children, so every time one updates, it overwrites the Epic and the Epic then keeps changing. That's not how it should work. 

You are going to have to do what I said then. Edit the values of each priority to add a number in front - whatever order you want. Then you can get what you want to achieve. 

Did you populate the End Date? And did it change on the Timeline? 

Hi Tomas - Welcome to the Atlassian Community! Correct, the End Date and Due Date fields are different fields. You could create an automation rule that populates the End Date with the Due Date when the Due Date changes if you like. 

Hi @坂下弥 - Welcome to the Atlassian Community! You can see some of that behavior if you are using Jira Work Management projects, but not with Jira Software projects. Not sure that will change any time soon. The other question would be why are there multiple people updating the same card at the same time? Maybe there needs…

Hi Kirsi, I would create a Jira work management project. Then you can create in simple intake form to handle the request. Then you could even create an automation rule that would clone the ticket over into the other project in Jira software, if needed. there is no extra cost for this.

Hi Hofit - Welcome to the Atlassian Community! I suspect you’re wanting to put the priorities in order by their severity more or less. But Jira put them in order alphabetically. So most people will do 1 – lowest, 2 – medium, 3 – high, etc. for the values. if you could share some screenshots of what you’re talking about,…

Great! Glad to hear. 

Not in the settings - in the form. When you are in the form, instead of just clicking on the dropdown, did you actually start typing the name of the Organization? 

You are very welcome. 

Can you answer all of my original questions though? 

Hi Vijay - Welcome to the Atlassian Community! You will need to contact the vendor directly for assistance. 

Hi @고상호 - Welcome to the Atlassian Community! Did you start typing the name of the Organization? Are you executing the form on behalf of a user? Or as an Agent directly? 

Hi Shoko - Welcome to the Atlassian Community! No, any user who is not an Active user will not count towards your license cost. 

Hi Sunish, You will need to submit a support ticket to Atlassian with that request. But realize that might not ever get changed. So in the meantime, you will need to adjust the value for each plan you create. 

Glad that is working for you. 

Hey @David at David Simpson Apps - Your article is out of Moderation. 

Hi Bala- Welcome to the Atlassian Community! We recently did this. You need to go into the issue type hierarchy, and they rename the Epic to Feature. Then go to your list of issue, types, and their rename Epic to Feature. While you were there, create a new issue type called Epic Now return to the issue type hierarchy and…

Hi Adrian - Welcome to the Atlassian Community! Make sure all of those statues are mapped to columns on your board. 

Hola Mesa. ¡Bienvenido a la Comunidad Atlassain! Ese usuario debe tener el permiso de Usuario asignable en el Esquema de permisos adjunto al proyecto. Y debe ser un Agente.