John Funk Community Champion

I see - I am not familiar with that add-on and what is available with the Create a Linked Issue function. You should check with the vendor to see if they have post functions as a part of the toolset or you will need another add-on like Automation for Jira or JMWE. 

Hi Leo- Welcome to the Atlassian Community! Issues (tasks) will go to the first Status in your workflow when they are created. In many workflows that is the Backlog status. You can create an automation rule that transitions the issue to another Status that is mapped to the Board if you like (just make sure there is a…

Hi @Karen Kelly - did you see Bill's response above? Can you share what you have that is not working? 

Hi @martinh You are creating the internal issue using automation for when the public issues is created? If so, then in your automation rule, set the Summary to: {{triggerIssue.key}} - {{triggerIssue.summary}}

Hey Romeo - did you ever get a solution for this? Did you try the API as Jack suggested? 

Hi J Mercado, You can't default it there, but you can create a filter that has the base information that you want. Then just start with that filter each time. 

So you copied my code above and it still does not update the field? If so, sub out now() for one of the dates and see if that works. 

Hi Mohamed, I suggest the Revyz Backup and Restore app from the Atlassian marketplace 

Ginger Ale is in my top 5

It was just right then 😂

Sweet iced tea - hands down!

Hi Sunil, What type of project are you using? Team-managed? Company-managed? Jira Work Management/Business?

Thanks for sharing!

Hello and Welcome, Dan! I would even suggest spinning up a free instance of Jira and use it for some personal things around the house - planning trips, events, etc. or handling hobbies like woodworking, gardening, etc. 

Hey George - Welcome! I am confident you will find some really good use cases for JWM in your organization - and even personal life! And glad you found your way back from Pivotal. :-)

Great! Glad it is working for you!

Hi @Catherine Swanwick - Were you able to get this sorted out? If so, what was your final solution? 

Hi @ST - HỆ THỐNG Check the Permission Scheme associated with the project to see who as the Assign Issue permissions. Then modify it as needed. 

Hi Prajwal, You should change the order of the fields on the create screen itself. Go to Settings > Issues > Screens and search for the create screen used by the project. Then reorder the fields on this screen. 

Hi @Raju Mandapaka - Could you mark the answer as Accepted so we can close this one out? 

@Bettina Funk - Woohoo, another Funk in the house! 

Can you post a screenshot of your actual rule? It's much easier for me to evaluate when I can see the visual. And tell me again the relationship between the issues? Is it just issue linking? Or is there a parent/child relationship?

Great! So it is working now? 

@Erodiane Souza da Silva Mais alguma coisa?

Great! Glad it is working as you would like. 

Sorry for the long delay in responding. Basically, you are going to be very limited using Team-managed projects (and therefore boards) to do that type of work. Your best bet would be to create a second board and see if that helps. Here is an article that will help walk you through how to do that. Give it a like if it…

If a rule doesn't trigger at all, it is usually because another rule is firing that would normally cause the second rule to fire. Be sure the box is check on the Rule Details page for "Allow rule trigger".

Hi Rajesh - You should be able to look at the Audit Log for the rules inside of the Automation for Jira app. 

Hi @Chris Covert I know this is very old, but did you ever get it sorted out? (pardon the pun). It's probably sorting on a date field. If you have the plan based on a filter, you should be able to modify the filter to include and ORDER BY statement. 

And the rule is firing but not updating the field correctly? Or what is happening?