John Funk Community Champion

Hi Mathieu - I don't work for Atlassian and don't know if they have any plans to even do it or not. You should create a support request with them directly: https://support.atlassian.com/contact/#/

There is no trigger type for Issue Cloned. Try this then: Issue Created (is this for just one project or several projects) Add a Condition: JQL Condition Use summary ~ CLONE for the JQL (assuming when you clone the issue that you leave the CLONE - text in the front of the Summary) Then clear the assignee. Would that work?

Oh, and is this a Next-gen project? Or do you use Next-gen projects? And if so, are there other projects that use the Closed status?

Can you post a screenshot of the audit log with the message?

But you are saying that it moves the issue to Closed anyway? So you are just getting an annoying message but everything works?

Hi David - Welcome to the Atlassian Community! I am not following your question. Can you provide a more detailed example?

@sreuter - any update on this one?

You can certainly do it automatically when the ticket is cloned. You would change the trigger type to Issue Created instead of Manual. Be sure to add any conditions if you don't want the Assignee cleared for all created issues. 

Hi @imtiaz.ali , You can do that with an Automation For Jira rule that would send an email when the value of the field is changed to high or urgent. Here is some information to get you started - it is a free product in Jira Cloud: There are two types of automation: * Global: In the Free version, you get 100 executions per…

Hi VA, Make sure that the atlassian-addons group has permission to Set Issue Security in the Permission scheme for that project. Also make sure that group is in the Administer Project for that project. 

Hi and Welcome Johanna! We are glad you are here!!

Hi @BZCC IT , I do not use Server version but in Cloud there is a post function for Copy Value from Other Field. Does that not exist in Server? If not, can you share a screenshot of the post functions available? Regardless, you should be able to do this with Automation For Jira. There is a free Lite version add-on for…

Hi Gabir - Welcome to the Atlassian Community! Can you share some screenshots of the problem in both boards?

Hi Neeta, Check the context for those custom fields. There might be a context where fields have a default value for certain projects. When it gets moved are the fields always populated with the same value across all of the projects where that is happening?

So what is the path you are taking to access the automation? Why type of project is it? Are you using the Automation For Jira add-on?

Hi @Дмитрий Афанасьев , Does it show up in the Old Jira Issue View?

Hi Carsten - Welcome to the Atlassian Community! Are there any Conditions or Validators on the transition to CLOSED? You might need to add the atlassian-addons group to the transition condition. 

You are welcome! I spend a lot of time building these and then submitting support tickets, reading, watching webinars, etc. The Automation For Jira folks are extremely helpful. Here's a little more information that you might not have: There are two types of automation: * Global: In the Free version, you get 100 executions…

Hi @shrikant maheshwari , How is the rule failing? Can you go to Audit Log to see what happens and what is failing? Can you share a screen shot of that and a screen shot of the rule itself?

If you choose the Clone option, then you just need to set the values of the fields that you want to change. The others will come on over from the trigger issue. 

Hi Nitya - Welcome to the Atlassian Community! Have you edited the Issue Type Screen Scheme associated with the Project to connect the screen to the new Sub-task type? 

If you know what your releases are going to look like as far as naming, I would go ahead and create those in your project. Then you just need to make sure you use those same exact value for the Sprint. So your rule would be based on a Field value changed on the Sprint field. Then you would do a new Action for Edit Issue…

Great! I hope it works well for you. :-)

So what is not working? Is it not firing at all? The problem might be that Next-gen Projects have separate statuses that build up. So when you select the Done status, you need to make sure it is the Done status for the Next-gen project you are working with. (You are probably seeing multiple Done statuses in the list to…

It is only going to show you Classic Software Projects because those are the only ones you can "associate" a board with. The Project is only there for showing it as a board in when in a particular project. It does not limit the board to tickets in that project in anyway whatsoever. That is done by the board filter. 

HI Roja, There is a free version of Automation called Automation For Jira Lite. It is an add-on but is free. The full version is a paid add-on. To see the differences in the products, refer to the document: https://confluence.atlassian.com/automation/getting-the-right-version-993924597.html

Hi Dany - Welcome to the Atlassian Community! Advanced Roadmaps are only available through the Premium subscription for Jira. Regular Roadmaps are currently in the second Beta for Classic Software projects. The Beta is closed to new users. But Roadmaps should be rolling out to all customers in the next month or two. 

Start with a Manual trigger (assuming you don't want to clone automatically based on some other trigger type :-) Then put in any additional conditions if you want. Then New Action - Clone issue. 

The link I sent is just information about the new top navigation from Atlassian. You can place comments there about changes you would like to see - like adding a link for all boards. :-) Another option is to just bookmark your list of boards in your browser. Here is the link: https://YourDomain.atlassian.net/jira/boards…

You can create as many boards as you want for a project. Just put the project in the Location field in the Board Settings.