Mikael Sandberg Community Champion

Hi @mo.phipps, Welcome to Atlassian Community! There are multiple ways you can construct your JQL to do this, the very simple would look like this: resolution = Unresolved Another example if you want to limit it to specific issue types: issuetype in ("Service request", Change) AND resolution = Unresolved And there is a…

What you are seeing is expected, the basic roadmap only support a single project. Once you add more than one project the basic roadmap will not work. If you want to see multiple projects in a roadmap you need to be on a Premium subscription, that will get you access to advanced roadmap which supports multiple projects in a…

Asset discovery is an agentless network scanner that can automatically import and update your assets.

You are correct, that is how the template rule is configured. But you can always change that so it works based on your requirements.

The short answer is that you cannot remove that field. If you are in a JSM project that field will aways be present.

Currently that is not possible, but Atlassian is working on granular admin rules and it is scheduled for sometime in 2023 based on the public roadmap.

You can control the users showing up in the user picker list by enabling user filtering, just go to Settings > Issues > Custom fields and locate the field and then click the three-dot menu and select Contexts and default values and you should see that option.

Have a look at this KB, Invite guests for external collaboration. Guests are free, but you can only have 5 guests per paid user, but the total number cannot exceed the current user limit.

Hi @Antoine McCord, Welcome to Atlassian Community! The documentation you found only applies to Jira Cloud, here is the one for Jira DC. 

You could use an automation that sends the email to the user, take a look at this thread. In order for the filter subscription to work you need access to the instance and also a Jira license.

Hi @Jana Gordes, Welcome to Atlassian Community! The way we do it is to either click on the icon for the issue type or using the move option. Both will open up the move action. And if you have set a default request type the move is simple, but if you do not have a default request type for each issue type, you will have to…

Hi @Rick Muller, Welcome to Atlassian Community! You can learn more about the different features in JSM here, and another good source is the Getting started guide. And you can also join the New to Jira Service Management group and ask any questions you have about JSM.

If you add the users as request participants they can view the request from the portal and will not see internal comments. If you give the user access to the agent view as a user you cannot hide internal comments from them, they will be able to see those and also add their own comments.

It doesn't look like you can set the Tier level via the API, but hopefully that is something that is coming in the future. For your second question, I would do similar to how I import data from our Endpoint Security tool to get our devices into Assets. We use an iPaaS tool for that and it iterates over each asset and then…

Hi @John Cross, Welcome to Atlassian Community! Currently team-managed projects should be seen as its own island with no connection to anywhere, which means that you would have status duplications, field duplications, etc. Atlassian is working on global custom field support, currently scheduled for Q3-Q4 2022 according to…

In order to do that you would have to link the question in the form to a Jira field, automation cannot access data within the form at the moment, this should change once the form API is released. Currently it is scheduled for Q1-Q2 2023 according to the public roadmap.

Just to add to Alex's answer, even without Atlassian Access this can be done, just go to Directory > Users under admin.atlassian.com.

You would need multiple statuses that has the approval step enabled in order to do this, since you cannot dynamically change the number of users that needs to approve it. And I would also probably hide the transition to these statuses for users by adding the Hide from user condition, that way it is only available for…

Advanced roadmaps only supports company-managed projects, but based on this suggestion it looks like that will change in the future, JSWCLOUD-20012.

In that case, the closest you can get to only trigger on that specific transition is to use the Multiple issue events. Yes, it will trigger on every transition, but that is as close as you can get. I did check and I didn't find a suggestion to have a trigger on the actual transition instead of the status.

Forms will support attachments in the near future, the public roadmap is showing that it is slated for Q4 2022 at the moment.

Have you tried using the Issue updated trigger for this? That should work since the transition is an update.

I looked a bit more into this and it looks like you can access services via the Opsgenie API, so you should be able to do bulk import via it.

Hi @Tanner Freeman, Welcome to Atlassian Community! Forms cannot be used in Atlassian Assist, it only support the request form. There is a suggestion to have this added to Assist, see JSDCLOUD-11678. 

Because the services object schema is locked you cannot do a bulk import to it unfortunately. 

Based on their documentation you have to either manually add items to it or use their CSV importer. If you are on JSM premium you also have access to Assets which has a discovery tool that can import assets automatically.

The short answer is no, you cannot currently filter services based on the project. Hopefully that will change in the future so you can use filter scope.

Go to Project Settings > Features and check if Post-incident reviews has been enabled.

You can learn more about the startOfYear() function here.

This filter would do the trick, it will get all feature issues that was resolved within the current year. issuetype = Feature AND resolved >= startOfYear()