Mikael Sandberg Community Champion

Hi @Wendy Lopez, Welcome to Atlassian Community! By default you can only have one assignee on an issue. You could create a custom field and add additional assignees, or use sub-tasks. You can set up issue security to limit what a user can see, including only allow them to see issues that they are assigned to. 

You will loose the reference to issues, since the new Insight for JSM is using a new field type. You can fix that by creating an automation that runs through your issues and sets the new field to the same value as the old one. Something like this: I ran it using a query in order to limit the number of issues for each run…

If the field is only required when creating the issue you can do that by creating a new workflow for bugs. If the field is set to be required in the field configuration you will have to create a new field configuration that makes the field optional and field configuration scheme that is associated with the bug issue type.

You could use groups, but from an admin standpoint you are better of using project roles in company-managed projects (team-managed projects only have three roles, admin, member, and viewer). In order to give a user access to only specific projects, for team-managed ones you have to make them private and then add users as…

salto.io allows you to version control your changes in Jira.

In the form, go to settings. From here you can enable the form to be visible on the portal and for which request types.

Short answer is no, fields are not version controlled.

If you want them to see the board they have to have Jira Software access. To prevent them from seeing other projects you will have to change the permissions on your team-managed projects to be private, and on your company-managed projects you have to change the permission scheme(s) to not allow anyone with access to browse…

Hi @Maria Truman, Welcome to Atlassian Community! In order for your client to see the board they also need to have a Jira license. If they have been added to your instance without access to Jira, they would still be able to see the project, as long as it is set to public. So what you are seeing is expected when you revoke…

Unfortunately, setting your team-managed projects to private is the only option. If they are set to limited anyone with access to Jira on you instance will be able to view and comment on issues in a team-managed project.

You can download all these reports if you go to https://www.atlassian.com/trust.

It can be done with Opsgenie, it has heartbeat monitoring.

Hi @Stephen Miller, Welcome to Atlassian Community! The short answer is no, you cannot have multiple hierarchies, it only supports one and applies to the whole instance.

Correct, once the trial period ends it will be part of the subscription that you are currently paying. You should also see next to the Install button the estimated cost that will be added to the subscription.

At a minimum you need to include the projectId, issuetypeId, summary, and any required system fields. Your other option would be to use the official Zendesk integration that Zendesk provides for free.

I assume you are looking for Scrum/Kanban boards correct? If that is the case you will only see those boards if you first go to the project, from here you will see the boards.

Hi @Liza Allison, Welcome to Atlassian Community! Customers are project specific, so if you want to create the customer in multiple projects you would have to do that via REST API. It has endpoints to get all customers in a project and to create new customers. So a potential solution would be to create all the customers in…

If you look at the top menu you should see one for Security This is where you can access Insights and Data residency

What link type are you using between HTP-352 and the others? By default the Advanced roadmap will only use the Blocks link type, but you can always changed that and add more link types as well.

Hi @[deleted], Welcome to Atlassian Community! Your site will be available for 15 days after your subscription period has ended, before being deactivated. Please see the Cloud Licensing FAQ for more information.

You could do this using the Send web request action to the REST endpoint for groups to get the members, and then add them to the field.

Hi @Bianca, Welcome to Atlassian Community! What you are seeing is expected, Trello and Bitbucket are not fully integrated yet with admin.atlassian.com, and that is also why you are not seeing Trello under Products. Atlassian has started working on integrating Trello, and the first thing that was added was Insights if you…

Hi @Heather Merk, Welcome to Atlassian Community! The basic view will only show dependency lines between issues in the same project. If you select the Dependency management view you will see the lines across multiple projects

What you are looking for is to add a screen on the transition that takes the request to the resolved status. If you are using the default ITSM workflow you will see that the transition to resolved has a screen associated with it. All you would have to do is add your custom field to that screen and if you want to make that…

Yes, if you go to https://jira.atlassian.com/secure/Dashboard.jspa?selectPageId=10440 you can add this suggestion under JSM Cloud.

Hi @Rachel Murray, Welcome to Atlassian Community! You could use quick filters to filter out initiatives from the Kanban board. If you use sub-filters it will also remove it from reports.

I just thought of a possible workaround. You could use just a generic transition and then on the transition screen have to user select which transition it is. It may not be ideal, but you could then use post function to clear that field when transitioning out form the destination status.

No, they do not have to be on the same deployment type.

Ah, I forgot that you where on Cloud. In that case your only option is to use Scriptrunner to set the label in a post function. Have a look at this thread for the script needed, https://community.atlassian.com/t5/Jira-questions/Is-there-a-way-to-automatically-add-a-label-to-an-issue-when-it/qaq-p/1054492. The thread…

The way we do it is to have specific fields that we want to be able to filter on sync over from Zendesk to Jira. Fields in the linked Zendesk ticket are not available to JQL.