John Funk Community Champion

You add the Admin to each of the security levels in addition to the group. 

Okay, thanks for the update. Have you opened a Bug/Feature Request for Atlassian to make that work in Forms? I would like to vote for that. :-)

Very good - thank you for replying and glad you found the solution. 

Hi Jayce - Welcome to the Atlassian Community! That's probably because your board filter does not have ORDER BY Rank on the end of the query. So edit your filter, add that on the end and save it. Then you should be able to rank the issues on the board. 

Hi Sumaiya - Welcome to the Atlassian Community! You can create a security level for each grouping off people - in other words, one for Finance and one for HR. Then add the appropriate people to each level for access. Then make sure that you set the security level at the time of the issue creation. 

You might try the Permission Helper inside the Permission Scheme to see what it says. 

Hi Katharina, I think you are thinking of Custom Fields - Statuses do not have those things. 

You are very welcome. 

If you add him to an Organization, he should be able to see all tickets tied to that Organization. He would need a Jira Software license to see more than that. 

Hey @Sam Zepeda Did Filipi's answer satisfy your need? 

I would go ahead and open a support ticket with Atlassian to see what they say. Please post the resolution back here so future readers will be able to see it. https://support.atlassian.com/contact/#/

Yeah, that's a weird one for me, too. And sometimes I still forget about it. 

Hi Markus - Welcome to the Atlassian Community! You will need to check the Permission Scheme for the project to see who has been granted the Manage Sprints permission. 

Hi Austin - Welcome to the Atlassian Community! The quick answer is yes. Create a project if you have not already - a Company-managed JWM project. Then modify the workflow as desired, save and publish it. This should cause the columns on your board to be updated. Rearrange the columns in the board as you desire as changing…

Hi Lucia, No, this is not possible because the values of the fields used by the X and Y axes must be in the same issue.

Hi Bruce As far as I know, they will stay there forever unless you delete them.

Hi Nisan - Welcome to the Atlassian Community! You will need a Jira Software Premium subscription in order to add levels above Epic. 

Does the user have a Jira Software license? 

Ah, it looks like this is not available in Server as it is for Cloud. Here is the request you should vote for and follow: https://jira.atlassian.com/browse/JRASERVER-66849 You might be able to do this with the ScriptRunner Behaviours add-on.

Sure - can you share the rule that you have so far, with the details showing for the email? But basically try using {{issue.status.name}}. Is that the only field you are missing now? 

Hi @Manoj You can try to create different Contexts for the custom field based on issue types. Meaning that you create a Context for one issue type and have a list of values for the field. Then create another Context for the same custom field but with a different issue type, then provide a separate list of values for that…

Please contact https://www.atlassian.com/trust/report-abuse

If those values are Request Types/Issue Types, then No, you can only choose one at a time. 

So if there is more to the rule, then check the Audit Log for the rule after you run it and it duplicates the post. Then walk through the audit log steps to see if it passes multiple IF statements - I suspect that is what is happening. You should see do places in the audit log where Microsoft Teams was updated. 

Hi @D.heijkoop - Welcome to the Atlassian Community! It's probably because they are Watchers on the project. There is a system level setting that makes users a watcher on any issue they interact with. It's best to turn that off. Go to Settings > System > User Default Settings Then edit the values to change Autowatch own…

HI Anita, What do you mean by "items"? 

Oi @Monica Aguiara - Você conseguiu isso para trabalhar para você? A resposta de Fernando respondeu à sua pergunta?

Hi Oliver - Welcome to the Atlassian Community! Yes, I would just create a board that shows issues from all 3 projects. The trick is that the 3 projects need to use the same shared schemes (primarily the workflow scheme). Which also means they all need to be Company-managed projects and none can be Team-managed. 

Hi Louange, To make someone an Agent, you grant them access to the Jira Service Management product in User Management. Or you can add them to the group for jira-servicemanagement-users. Or take them out of that group to remove them as Agents. Neither will change the access to the issues if they have Jira Software licenses,…

Also echoing Bill's comments and others. Definitely need a better search function, especially by date. Need a way to identify the exact rule that was executed that caused an action to happen. IOW, each rule should have an ID, then in the History of the Issue, it should denote which Rule ID was the one that fired to cause…