Mikael Sandberg Community Champion

The Assigned to me queue is not unique to each user when it comes to columns etc. If you make a change to it it will affect all agents that is using that queue. In order to create individualized queues you would have to create one for each agent in your project and replace currentUser() with the agent name.

In the report you would see the detailed status, the customer visible statuses are only applied to the portal, nowhere else. You could work around that if you had an app like Custom Charts since that allows you to rename the statuses in a list view. If you go the custom field route, you would have to either set the client…

As far as I am aware there isn't specific documentation that covers JSM project for new data requests, but there is a project template for Analytics service management that you could start with. And if you have Atlassian Intelligence enabled for JSM it can help you suggest what request types you should have. My BI&A team…

Hi @Greg Costa, Welcome to Atlassian community! If I understand your question correctly you want the customer to see the cloned request when they view the original on from the portal correct? The request form cannot view the linked issue, so if you want to let the customer know about the linked issue you would have to add…

Hiding/renaming the statuses that the customer sees in the portal doesn't effect what the agent sees in the queues. So for if example you have a status called Escalated, but you rename it to To Do for what the customer sees, your agent would still see Escalated as the status.

Hi @james.maida, Welcome to Atlassian Community! You can hide statuses from the Portal by renaming it on the request type. See my answer to a similar question. 

No, that is not possible to do currently. Once a user have access to the project they will see all visible request types on the portal for that project. The only way to do this would be to have separate projects and then control who have access to the project. There is a suggestion to be able to do this,…

I know that this suggestion is only mentioning moving within a schema, but once that is solved then moving between schemas should be feasible too.

Hi @Kenny Fairlie, Welcome to Atlassian Community! Currently that is not possible, but there is a suggestion to add this feature, see JSDCLOUD-10000, that I would recommend that you go and vote for and follow.

Natively in JSM/Jira this is not possible, labels are global within your Jira instance. You would need an app in order to do this, there are couple of label managers in the Marketplace.

SLAs are applied to issues based on the JQL you have defined in the SLA goal. So in order to apply your SLA to all incidents you could do something similar to the SLA for normal changes. Just change the the JQL to be something like this: "Ticket category" = Incidents This would pick up all Incidents request types. If you…

It is not possible in a screen, but you could do it by using Forms. Forms allow you to create dynamic sections that are only visible based on selected values in a question. 

Check out this KB for more information, https://support.atlassian.com/jira-cloud-administration/docs/manage-issue-screens/

Go to Project settings > Issues > Screens, from here select the screen scheme that belongs to the issue type you want to rearrange the screen for. This will take you to the screens and from here you can go in and reorder, add, and remove fields. If you only see one screen for the default one you will have to create a new…

You cannot use tagged users, the permission scheme do not have an option for it, so it has to be either a group, project role, single user, or a field.

Hi @Habib Memon, Welcome to Atlassian Community! You could use the request participants field and then add that to your permission scheme so you can allow other users to see the request. If you do not want to use the request participants field then another option would be to create a new user field and add users to that if…

You can modify the create screen if you go to Project settings > Issue types and from here you will see the screen scheme that the issue types uses. If you click on the scheme it will take you to the screen that shows you the screens used for default, create, and edit, and if you click on the screen you will be able to…

Yes, it is possible and can be done in a couple of ways using automation. The first one would be an automation that makes a call to Okta to get the reporting manager. Another option if you are JSM Premium and are adding your users to it, you could then do a lookup object in the automation to get the manager that way.

It all depends on what customer permissions you have set in the project. If you go to Project settings > Customer permissions you can enable sharing

Hi @juan.aguilar, Welcome to Atlassian Community! It all depends on what type of project you are using. Approvals are only available in Jira Work Management projects if they are team-managed. But there is a workaround by using automation, custom fields and circular transitions. Have a look at this article that I wrote…

Correct, org admins can also do this. But you should always think what is the minimum permission needed in order to do something when answering a question like this, so therefor product admin is the correct answer.

Hi @Siddharth Verma, Welcome to Atlassian Community! There isn't an API that will give you the overall status, but you can use Get a list of components to get all the components and statuses and go from there. 

And you cannot use approvers group for this, you would have to use the approvers field instead which is a user picker field.

Yes, that is possible. You have a couple of options to do this with automation. You can either use a lookup table in the automation that specifies who the approvers are based on the group. If you are on the premium plan or higher you have access to Assets and can use that as your lookup table to get the approver(s).

Hi MS, Welcome to Atlassian Community! In order to create a role and set the group you only need Product admin permissions, so option A is correct. You would only need site admin if you also needed to create the group as well.

Hi @juan.aguilar, Welcome to Atlassian Community! Yes, it is possible and as @Dan Breyen mentioned this can be triggered on issue changed, but I would recommend using Issue transitioned instead since you can then make it more granular. Here is a good resource to get started with automation. 

If you are on the Premium or Enterprise Plan you can now use page conditions instead of the CQL, see the new announcement about it here.

This might change once Atlassian Guard Premium becomes available.

Hi @Elias Federico Bourda Jorge, Welcome to Atlassian Community! You have to be on the Enterprise plan in order to prevent anyone with a managed account to sign up for a new product. For all other product plans your only option is to get notified and then be added as an admin in order to remove the application and then…

Hi @edwardcorreia78, Welcome to Atlassian Community! Yes, that is possible with automation. All you have to do is create a scheduled automation that looks for issues that haven't been updated in the past 7 days and then either add a comment on it or sends an email. Here is an example from the template for JSM: