Mikael Sandberg Community Champion

What you see is correct, if you do not have an manually triggered action that is what you see. Once you add a manually triggered action/automation you will see it listed instead.

No, you cannot add a hidden field that has the portal group in it. I brought this up with the product team about a year ago, and the response was that the group is just a way to organize your request types and that is where the relationship ends. There is no way to extract the group so you can use it somewhere else.

Okay, so the user need to have a Jira license on the domain where your JSM project exists, licenses do not cross domains.

Okay so if you click on the issue key again, that will take you to the detailed view instead of the hovering one. Now if you click on the issue type icon you should see all the issue types in the project. Then just select the one you want to move to. If the new issue type is on the same workflow it will just do the switch.…

Hi @Terri Tobin, Welcome to Atlassian Community! Does both issue types, the current one and the new one you are trying to change to, use the same workflow? If the answer is that they are using different workflows then you would have to use the move option in order to change the issue type. 

Here is a good page that gives you an overview of how all the schemes work together. It is from the DC/Server documentation, but the same thing applies to Cloud.

The field configuration scheme will only remove the field from the screens, you would also have to your field configuration (go to Project settings > Issues) and either make the field optional or hidden.

The short answer is that it cannot be done, the group is not stored anywhere.

Another attribute, that way you can use a filter to say only show desk.

Since your second automation is triggered by the first one, make sure that you have checked this check box under rules detail.

You cannot create a nested query needed to get the result that you are looking for without using an app that extends JQL with a function that can do that. I know from experience that both Scriptrunner/Enhanced Search and JQL Tricks can do this, but you should also look at some of the other apps in the marketplace that can…

Hi @Emily Seage, Welcome to Atlassian Community! Have you verified that the user in question have a Jira license? If they do then they should not be redirected to the portal, instead they should get a permission error. If the user goes to Projects > View all projects and select Jira Service Management in the product…

You should be able to this by using two automations, similar what is described in this article about dynamic looping in automation. You could use your first automation that you have to kick of the second one and in the web request include the issue key for the epic. In the second automation you would look up the parent…

I would probably go with your first option, and either use a label or a prefix like you suggested.

There is a suggestion to have this feature added, CONFCLOUD-5876, that you can go and vote on. 

Hi @daniel.rivera2, Welcome to Atlassian Community! Templates do not have a page history like pages do, so there is no option to revert changes to a template.

You would need something like Scriptrunner and Behaviours in order to make the field read-only. And regarding the None option, the only way to remove it is to set a default value for the custom field.

Hi @Sureka SounderRajan, Welcome to Atlassian Community! You can do this by changing the permission schemes that your projects are using to not allow any logged in user to browse projects. You should instead use a project role for it, that way you can manage access to projects by adding the users to the role within each…

Are you adding the comment in the request channel or the triage channel? For it to work you have do it in the triage channel. Here is the documentation for it.

No, the attribute reference can only be a 1-to-1 relation, so you cannot set the attribute to reference Desk, Server Room or Off Site, you have to pick one of the three. And you if you would create the location as an abstract object schema your reference cannot use that to pick objects, it would show up as an empty list.

You cannot change the default notification that is sent out, but what you could do is change your notification scheme to not send an email when issue is created/assigned, and instead use automation. By using automation you can control what fields should be included in the email.

Hi @Arianna Harrison, Welcome to Atlassian Community! You could do this by setting entity properties on the project when it is created, and then use that in the automation to create the stories. This would require that you either create the project via REST API or manually add the property after creating the project, since…

So that looks like you are using Table Grid, and based on a quick look at the documentation you add a field to the screen in order to show it. I am not 100% that you can add it to the create screen, it looks from the Quick start guide that you can only add it to the view screen. But I would contact the app vendor to find…

Hi @Batuhan Dogan, Welcome to Atlassian Community! It sounds like you have at least two screens associated with the issue type, one for create and one for default. If you go to project settings > screens you will find your screen scheme that it issue type is associated with. The one that is set to the default is the one…

I agree with everything @Jimmy Seddon said, and one advice that I learnt after my first Summit/Team back in the days (this year will be my 7th) is to not try to attend all the sessions that you find interesting, they will all be available virtually after the event as well. Plan some time to walk around the expo hall and…

You need to update your existing permission schemes so they do not allow any logged in user to browse projects, and instead use project roles. That way you allow the project admins to control who should have access to the project by adding users/groups to the right roles in the project. You can learn more about permission…

If you go to Project settings > Workflows you should see all the workflows used and which issue types are associated with each workflow. 

This happens if the two issue types are using different workflows, the only time you get the instant change is if both issue types are associated with the same workflow.

That is the new issue view, it moved the security level from showing as a field on the right to now using the pad lock icon. Here is a KB that shows the new location.

The short answer is no, you cannot change the breadcrumb path to show the summary instead of the issue key.