John Funk Community Champion

Hi Suzi, If the Form field is mapped to a Jira field, absolutely you can report on that or create Automation rules that use the value when it is changed to No. 

Hi Sandeep - Welcome to the Atlasssian Community! Yes, that is possible to create using Automation rules. Create a rule based on an Issue Created trigger. Then add any conditions needed. Next add a new action(s) to create the sub-task. You might could keep branching there (create a branch for Most Recently Created issue)…

Hi @이소원 - Welcome to the Atlassian Community! Have you tried with another browser? Or with Incognito mode? 

Hi Marco, What do you mean by "if the archive project does not have these fields assigned"? If the fields are there now, they will not become unassigned because the project is archived. The fields will still be there and the values available. If you remove the fields or take the project out of the context if it is in…

Hi Dee, Not sure that there are plans to incorporate the UI from JWM to all of the other products. Atlassian tends to keep the products separate based on their function. I, too, wish we could have almost a buffet of features to pick from for each product. Maybe that will come one day. In the interim, yes, you can create…

Great! Glad you got it working. 

Glad you got it working!

Great, thanks for sharing that. For your example, and the one that you did and got the error , what was the status of the epic and to which status did it go? And for everything that’s linked, how many were linked? And what was the status that each were in at the time the epic transitioned? 

Are the cards in another swim lane above that swim lane?

Hi Samuel - Welcome to the Atlassian Community! If the linked issues are not the same issue type, they might be using a different workflow which has different statuses. Or the linked issue might be in a status that cannot go to the same status as the trigger issue based on the transitions. Can you verify that all issues…

What doesn't work about it? 

Is this workflow used by multiple projects? 

You might be able to get by with color coding the cards, depending on the number of unique possible combinations. Otherwise, it will probably be quick filters. 

Hi Sayali, Let me see if I understand this correctly. You created a new Jira Software Kanban board (not a Scrum board) - correct? And the filter used by the project is simply Project = ABC ORDER By Rank Is that correct? But you don't see all of the issues on the new board? Is that correct? What issues are missing for you?…

I don't use the Server version but I have seen this problem in the past as it often relates to a duplicate issue ID that somehow happens. Try to follow this diagnosis and solution: https://confluence.atlassian.com/jirakb/indexingfailureexception-thrown-during-reindex-of-jira-server-779158905.html

Sure, you can try that. Go to the Field Configuration Scheme used by that project. Search for the Description field inside of the Field Configuration. Then click on Renderers. Change the Renderer from Wiki-style to Default Text Renderer. Click on Update. See if that makes a difference for you.

Great! Glad you got it working. 

Great! Glad that worked for you. 

Sure, click on the All transition to Done (the line that goes to Done). Then when the popup box comes up to the right, click on Post Functions. Then click on Add Post Function Then select Update Issue Field and click Add Select the Resolution field. Then change the Field Value to Done. Click the Add button. Be sure to…

Understood. If you end up deciding that you need the functionality, the article should help. 

Hi Vicki You need to add a Post Function to the new transition to Done that sets the Resolution field. 

Can you share a screenshot of the transition with the details? 

Can you post the Audit Log for the results after you run it? 

Hi Sidar, Yes, this is the normal behavior that I have seen as well for many years. 

Great!

Hey @Roopa Dass - I am marking Tharaka's answer as accepted. Let us know if you still need something with this one. 

Hi Sidar, If you use the Validator, the user can still see the transition and would just get an error if they don't meet the parameters of the Validator. If you use a Condition and the user does not meet the Condition, then they will not see the transition at all. Which I think is what you want. 

Hi @afe ccd - Welcome to the Atlassian Community! Try {{issue.Story Points}} - Returns the issue's story point estimate (company-managed Jira Software Cloud only). {{issue.Story Points estimate}} - Returns the issue's story point estimate (team-managed Jira Software Cloud only). Make sure you use the right case because it…

No, go ahead and contact them here: https://support.atlassian.com/contact/#/