John Funk Community Champion

Hi Jiten, Can you share your full rule here? 

Hi Adem - Welcome to the Atlassian Community! No, unfortunately once they are deleted, they are gone. If you have a backup from a particular date, you could try to retrieve, but you would lose all of the recent changes. For the future, I would get an app like the Revyz Back and Restore app which will let you restore…

HI Narayan - Welcome to the Atlassian Community! You cannot move projects from one template to another. You have to create a new project with the template that you desire. And then you would need to migrate the issues from the first project to the new project. 

Hi Jongun - Welcome to the Atlassian Community! Create an automation rule with a Scheduled trigger to run once a day. Then add a JQL query to the trigger for Project = ABC and Created = -8w

Team-managed projects use the Parent field and not the Epic Link field. Also, the CSV import function is intended to be kind of a one-off function, not a continuous way to create issues. 

Is the parent shown on the board and just in a different column? Or you don't see it on the board at all? Also, what type of project is this? Team-managed? Company-managed?

Hi @andtaylor - Welcome to the Atlassian Community! Most likely it's because it is a board associated with a Team-managed project and those boards cannot be copied as Team-managed projects are self-contained. If you want to create a second board for a Team-managed project, you can follow the guidance in this article:…

Hi Jasmine, Use {{triggerIssue.key}} for the value in the Epic Link field. 

Hi Adnan - Welcome to the Atlassian Community! You will not be able to get the date assigned out of the box with Jira. You would need to create a custom date field and populate it when the issue is assigned to you. 

Hi Pim, Are you sure the Resolution is not getting set? I don't see how/why the Satisfaction email would get sent without the Resolution getting set. Please check the history of the issue to see if something is there. 

Hi @C Anuradha - Welcome to the Atlassian Community! You can create an automation rule that will transition the parent to Done when all of the sub-tasks are done. See this example of how to do that. https://www.atlassian.com/software/jira/automation-template-library/rules#/rule/112177

Hi Vanvisa - Welcome to the Atlassian Community! You will need to open a support ticket with Atlassian. https://support.atlassian.com/contact/#/

Hi Sello - Welcome to the Atlassian Community! They should be able to see it already now if the products are in the same instance. 

Well once again automation doesn’t sort anything. There is an event that happens and automation responds by performing an action. Sorting isn’t one of those actions. Can you provide specific step by step actions that you are taking and what you expect to happen?

You are welcome.

Hi @Aswathi D - Sorry, I can't. Would like to know the answer myself! You might be better off contacting the Tempo vendor directly through their support. 

Hi @faizajannat028 The reason that you can't just change the Issue Type from one value to another is that they must be using different workflows. If both issue types used the same workflow, it would let you change the value. So you need to do the Move function to move it from the Task issue type to the Epic issue type.…

Great! Glad you got that sorted out. 

What type of project are you using? Team-managed? Company-managed? 

Hi Caryn, Jira Service Management projects are designed for Help Desk teams or teams that function in that type of environment. So Project Plans as such would not really apply to them unless I am missing something. Also, Jira is designed more for Agile practices, not Waterfall. You might try using an add-on that provide…

Thanks for the clarification. You will not be able to get that out of the box with Jira. Maybe a workaround like creating a custom field (single picker drop down type) with different values for each timeframe. Then an automation rule that would populate the value of the field based on an Issue Created trigger and the…

@Sari - Did you try to implement Mikael's suggestion? 

Amanda! Awesome how you are putting JWM projects to such good use. Win-win is always a wonderful thing!!

About time you showed up here @Dave Mathijs !! Happy to see you here and looking forward to your thoughts on Jira Work Management. :-)

I have no idea why this would fire twice on the same issue for an Issue Created trigger. I suggest you contact Atlassian support to see what is going on. Please post the resolution back here for future readers. https://support.atlassian.com/contact/#/

You did this same thing on another project using the Issue ID as a number like that and it worked? 

Hi Bastien, Is you use a Proforma form instead of the built-in Request Type form, you might be able to do that. While in project settings, click on Forms - then create your form. 

Hi Chloe - Welcome to the Atlassian Community! Did the user change the subject line of the email when they replied? Did they just hit reply and type in a new message in the body? Or did they do something else? 

Hi Abhishek - Sorry, but you will not be able to do any of those things with an Automation rule. 

For steps 1 and 2, since there are so many people, I would change the Approval step to use the Approver groups field instead of the Approvers field. Then put in the group that contains the appropriate people for each status. Let's do that first and see if that works for those steps for you.