Mikael Sandberg Community Champion

Hi @R M, Welcome to Atlassian Community! It sounds like your Jira admin added a custom field called Regression. If you do not see it anymore the field has been removed from the screen or removed.

No, JQL doesn't allow you to do that. You could use automation and a custom field, and every time you start a sprint you could update it with the number of sprints each issue has in the sprint field. The smart value would be something like this: This example only logs the size in the audit log for the automation, but you…

@Glen Cochrane Correct, it would indicate that the the assignee is the resolver. You could use automation/post function to set the resolver, either in it's own field or by using the assignee field.

Hi @Greg Bammel, Welcome to Atlassian Community! You have a couple of options to do this. You could use automation to do the calculation via smart values and math expressions. Another option would be to use something like Scriptrunner, it has calculated fields that you could use or you could write a script that does the…

You can do this if you go to Services, select the service you want to change and then click on the three-dot menu up in the right-hand corner and select edit. That will bring up a window that allows you to make changes. 

Have a look at the documentation for Opsgenie with MS Teams, at the bottom you have a list of commands that can be used.

Out-of-the-box JQL does not allow you to do nested queries that is required to get parents and all their child issues. You would need an app like Scriptrunner/Enhanced search or JQL Tricks which enhances JQL to allow you to do that. There are also other apps in the Marketplace that can do this.

project = JRA AND sprint in openSprints() AND issuetype != sub-task will remove subtasks from the result.

Hi Jane Smith, Welcome to Atlassian Community! The assignee field is expecting the Atlassian Id of the user that should be the assignee, so using {{issue.description.substringAfter("Assignee: ")}} would only get the name of the user. You would then have to search your users via the Find user endpoint in order to get the…

No, they would not have to have JSM licenses in order to do this. What you could do is add them as request participants, that way the leadership team would be able to add comments via the portal, which does not require a license.

Hi @Nancy Corsi, Welcome to Atlassian Community! project = JRA AND sprint in openSprints() will give you all issues that are associated with the current active sprint.

Hi @Samira, The number of users for the app has to be the same as the number of users that you have for Confluence. You cannot choose a lower number for that app. Please see this FAQ for more information. 

The short answer is no, you can not hide the backlog column and still have access to the Backlog board. You could work around it by using two boards, one that have the backlog feature enabled and the second one that doesn't.

If you check the audit log, what does it say when you get to checking if Accountabilities is not empty?

Okay, instead of the issue field condition, use the JQL one see if that helps, similar to what I did in my test automation above.

Yes, that is possible. What you need to do is update the notification scheme that your project is using to include the users from the custom field. Please see Configure notification schemes for more information.

Yes, that is correct.

It all depends on the endpoint and what permissions you have, but most of the API endpoints require that you have a JSW license and the right permissions in projects. Setting Any logged in user in the permission scheme to for example manage sprints would only allow users that have a JSW license to manage sprints, since…

Hi @HALL 9000, Welcome to Atlassian Community! Have a look at this tutorial, Gitflow Workflow. You will also find a lot of other interesting tutorials and articles at https://www.atlassian.com/git 

Hi @Steve Novotny, Welcome to Atlassian Community! Branches are just pointers to different parts of the history and removing a branch will have no effect on the size of the repository, since the history of the large files is still in it. The only way to remove large files from the history is to clear the history out. You…

You cannot add additional queue categories currently. There is a suggestion to add a feature to allow you to group queues, JSDCLOUD-285, go and vote on it if you would like to see it implemented. 

The difference is that any logged in user applies to all users that you have on your Atlassian instance, so it could be your Confluence users, JSM agents, and Jira users. Application access - Jira Software is only for users that have been assigned a JSW license. For external access there are are couple if different ways,…

What is not working, the JQL or your automation? I just tested this automation in my sandbox and it works as expected: Some of the components do not support searching on empty values, like the issue lookup one, but the JQL condition in the if/else one does support it.

Hi @Andrea Dieguez, Welcome to Atlassian Community! In order to change the billing information you need to be a site admin. If you do not have anyone that is a site admin you can always contact Atlassian support and they can help you.

Hi @Marcus Jones, Welcome to Atlassian Community! Atlassian just rolled out a new feature that allows you to hide projects from the portal and still be able to receive emails to it. Just go to Settings > Products > Jira Service Management > Configuration and from here you can customize the portal and hide projects. See…

Assets doesn't have a direct integration to Intune, Meraki and/or ITGlue, but you can always create your own integration using the REST API. Before we switched to Kolide we imported data from both Intune and Jamf into Assets using tray.io to do it. After switching to Kolide we are getting all data from there instead of…

Hi @Mansi Desai, Welcome to Atlassian Community! You cannot show Jira Software issues in a Work Management project, you can only do it the other way by showing Work Management issues in a Software project. 

You should be able to do it by using the JQL condition, something like this: description is not EMPTY

It can be done, but you need to be on Jira Software Premium plan, which gives you access to issue hierarchy above the default Epics - standard issue types (story & task etc) - sub-task. Or you could use JXL from the Marketplace which also allows you to configure your own hierarchy.

The only other way, if your Jira admin doesn't want to create a new group would be to create a distribution list that you could use instead, like projectx@example.com.