John Funk Community Champion

Hi @Krishantha is this a company managed project or team managed project? To change permissions for a company manager project for project rolls, do you need to edit the permissions scheme. Changing the administer project permissions for the project roles should clarify things.

Hi Dwight, If there is something unique about the issues, then you can limit your query that way - such as are all of them or on the same project or multiple projects? Perhaps run the query to see how many your return using the create date, etc. 

What a fantastic site for all kinds of Atlassian resources! I recommend a good featured book 😊

Hi Julius - Welcome to the Atlassian Community! Not sure what you are actually asking. But in general, a rule will fire and an action will happen. Whether there is follow up by a user is outside of Automation capturing that - unless, of course, you create a separate rule to fire when the user performs another action. 

You should be able to do that in one rule using multiple Conditions and/or Branches. 

Hi Manoj, Groups are used throughout Jira and are maintained by Site Admins (you add a user to a Group in the User Management settings available for Site Admins). Groups can then be used to grant permissions to those members for the group. Project Roles are specific to the project and users must be in the appropriate…

Hi Linus - Welcome to the Atlassian Community! No, you will not be able to edit the standard message. But you can create a separate Automation rule that will send an email to the Assignee when that field changes. I the Send email action, you can place whatever you want in the message. 

Sure - Create two transitions from the status A to status B where you want to check the field. Place a Condition on one of them where the Priority field = whatever value that will trigger the mandatory field. While there, add a Field Required Validator to that same transition that the Work notes field is required. Next add…

Hi @beacon.grayson - It is better if you create a new question in the Community. That way more people will see it and respond, and specific details to your situation can be discussed. Please post your full rule with the new question, especially showing the details of the field update in the Edit Issue component. 

Hi Guru, No, this is not possible out of the box as you describe. The only add-on that I am aware of that could do that is ScriptRunner Behaviours app. However, you could add a Validator to a transition in your workflow (or multiple transitions) so that the field is required to transition the issue if the Priority field is…

Correct. The Permission Scheme uses the Project Role (e.g. Developers) to grant a permission (e.g. Browse Project). Then within Project ABC, Joe Smith is added to the Developers role. He can now see issues in Project ABC, but not in any other project that uses the same Permission Scheme. If you want him to see issues in…

Yes to what Nic says, and I would add that you should put company policy in place that says that Jira Admins should not add themselves to sensitive projects without prior permissions. You can't control if they do, but then it would be grounds for discipline if they add themselves. So for the HR project, only the desired…

Project Role assignments are unique to each project and only apply to that project. Your Permission Scheme can (should) grant permissions to various functions in the Scheme. Then for the project that you want to grant access/permissions, go to Project Settings for the project (you must be a project administrator). Then…

You might try turning off the Backlog function and then turning it back on. I am not sure what built-in functionality that Team-managed projects are using for setting up the Backlog function. But I would assume it would use the first Status in your workflow. Can you post your current working workflow now? 

Hi Hines, What is not working with the rule above? Do you get an error? Or does it just run and nothing gets copied? Also, it might just be how you copied it, but it appears you are missing and ending } in your JSON. And you don't need the JSON and the copy from field - you can remove that and just try with the JSON. This…

Hi @prakash - I am marking Trudy's answer as accepted. Please let us know if you still need assistance.

Hey @Jimmy Seddon - I can do May 12.

I will take May 22nd

Hi Kerrie - Welcome to the Atlassian Community! Take a look at this article to see if it helps you. https://community.atlassian.com/t5/Jira-articles/Creating-a-Flexible-Recurring-Task-Issue/ba-p/2040862

No, only in that project. 

Hi Khushi - Welcome to the Atlassian Community! A Jira Administrator will need to grant that permission to you and n the System Settings. Go to Settings > System > Global Permissions 

Hi Sam - Welcome to the Atlassian Community! You can use a shared single Permission Scheme and control access by what Project Role you put the user in.

Hi Breanna, Yes it would be a series of If/Then conditions.

you can turn that off by going to Settings > System > General Configuration Scroll to the bottom and turn off the product recommendations

Oh yeah, forgot you were using Team-managed project. It is probably forcing the first Status into the Backlog section. If that is the case, you will need to change the workflow to use the Backlog from the Create transition. Then you could do the Automation rule for the auto-transition. 

That's probably because the TO DO status is mapped to the Backlog column. You need to add a status of BACKLOG between the Create transition and the TO DO status. Make sure you add a transition from TO DO back to BACKLOG if you want to move the issues back and forth. All of that assumes you want to use the Backlog…

Thanks for the update - but no one will be able to access individual issues in your private instance. I suggest you do the above to turn off product recommendations and see if that helps. 

Hi @Angélica Luz ! A user asked on another post that if you exceed the 100 emails in a day, the support article says that further emails are paused until the next day. Does that mean that no more emails for the day will be sent period? Or does that mean that the next day, the excess emails from the previous day will be…

Hi Maja - Welcome to the Atlassian Community! When you create an issue, it goes to the first Status in your workflow. That is typically the Backlog status. But that status is not in the first column of the board if you implement the Backlog function. So, you need to create an Automation rule to transition the issue to the…

You could probably set it up to an issue and set the Recurring Need custom field value mentioned in the article. Then create another rule that clones that issue when an issues is created with that value in the custom field (I would used Monthly) but also add a condition that limits the creation based on a time period for…