John Funk Community Champion

You shouldn't use a Field Value Changed trigger for Status, you should use an Issue Transitioned trigger. 

Great! Glad it is working for you. 

Great! Happy to help. 

Hi Emma, Try moving the Link issue action under the Create issue action. Then change to link it to the Trigger issue. 

Can you share the rule that you have so far? 

Yeah, you would need ScriptRunner for that. 

Add JQL to the scheduled trigger part to make sure there are linked issues and the issue is not Done. 

Hi Daniel - Welcome to the Atlassian Community! Go to Settings > System > Global permissions Remove the Site Admin from the Administer Jira permissions. Then also make sure the Site Admin group is not used in the Permission scheme at all. Be sure to test it with someone to make sure they can't see the project or any test…

Hi Christian, That's very strange. Are you able to click the Assign link and assign it to the Project issue type? And then remove the Sub-task? 

Hi Vishnu, You shouldn't need smart values for the trigger for Statuses. Just add the condition for Issue Fields Condition, choose Status for the field and then Is One Of for the second listing. Finally add the status values. 

Hi Riina, You can't use = with the Time stamp one because it would try to make the value equal to an exact time as well as the date, which it cannot do. You will need to use something like >= or <= (or maybe even just < or > ).

Hi Darren - Welcome to the Atlassian Community! You can copy the current one based on the When Issue Linked trigger and change the trigger for the new one to a Scheduled trigger to run for the existing ones. But make sure your first rule is working as intended before you copy it. 

Hi Ahmed - Welcome to the Atlassian Community! With a Free account you are not able to control who can see what - everyone has access to everything. You would need to upgrade to a paid account to be able to do that. 

Hi Pelerin, You won't be able to do that during the create process with the Description field. You can create a new paragraph (multi-line text) custom field. Then go to the Field Configuration for the project and edit the field to change the Renderer to Wiki-style. Then you can modify the Custom Field to add a Default…

Awesome - glad that worked!

Okay - it must be setting that prior to recording the parent. The triggerIssue is actually what I use the most myself. And if you want the parent ID, just use {{triggerIssue.key}}

Hi Casper, No, that is currently not possible. But there is an open change request that you can vote for and follow. https://jira.atlassian.com/browse/JRACLOUD-3406

Hi Reehamehra - Welcome to the Atlassian Community! You must be a Project Administrator to see and access the Project Settings link. 

Great! Glad it is working for you. 

You can have an admin on the current board copy it for you, or make you an admin on the board. 

Hi Viral, Try using Legal Review - {{issue.parent.summary}}

Hi Rachel - Welcome to the Atlassian Community! You will need to be a Board Admin or a Project Administrator to be able to see the 3 dots menu. 

Hi Kim - Welcome to the Atlassian Community! I would add a custom field - something like a Radio button with a default of Yes. Then when your agent creates the ticket, they can change it to No. Then add a Condition to your current Automation rule to check to see if the value of the custom field is Yes. You could also do it…

Hi Jack, Make sure that the field is on the Edit screen. 

The user would have to consume a Jira Software License at the least to be able to see Issue Security issues. 

Hi Vera, Why are you using Automation and not the built-in Approval by Email function? 

Hi Bjarke, You should be able to add an Organization to your project. Then add the user to the Organization. Then they should see all tickets that get created for that Organization. 

You are welcome.

You are welcome. 

That is up to you, but they definitely work different. For Team-managed click on Issue Types first then select Edit Workflow.