Mikael Sandberg Community Champion

I would recommend using the Components field for this, and the reason is that you can then auto-assign the request to the lead for the selected component if you want. As of right now Services are only visible to JSM agents.

Hi @Aytac Caliskan, Welcome to Atlassian Community! The resolution field is a system field that you should only add to a screen when transitioning to a done status, or just use post functions to set it. It sounds like your workflow allows you to move between different statuses freely, so you need to make sure that when you…

Hi @Von Shep, Welcome to Atlassian Community! We do not have any insight to the Jira instance that ADP is using, this is a community mainly made up by customers using Atlassian products. You need to contact your IT department to get your login credentials.

This is a good page to see how it all fits together, Project screens, schemes and fields 

Adding a screen to a transition is done in the workflow editor. You can add the screen either when you create the transition, or if the transition already exists you can edit it and add the screen. Please have a look at this KB for more information.

If you look in the Automation library you will find a rule for this that looks like this You can also find more templates here, https://www.atlassian.com/software/jira/automation-template-library#/

For the automation that creates the clone, make sure that you click the check box under Rule details that allows other Automations to trigger your rule

As @Pramodh M mentioned the affected services field is only visible to JSM agents. The workaround is to use either the components field or a custom field that is visible to the customers and then use Automation to set the Affected services field. 

No, to export the tree structure to PDF or Word you would need an app, like Scroll PDF or Scroll Word Exporter. 

Oh, you are using a team-managed project. Unfortunately your cannot use a screen to set the resolution in those project. And the only resolution that will be set is Done, and it is done when you move the issue to the far-right column. Currently it is only company-managed projects that allows you to select the resolution.

If I would implement something like that I would lean towards using Insight, since it would be much more easier to maintain than using user properties.

I have two solutions that comes in mind that might work for you. The first one would involve Insight in JSM, so you would have to be on the Premium plan. You could then set up the structure in Insight and then use Automation to get each approver. The second solution would use Automation and user entity property, similar to…

Hi @Majida, Welcome to Atlassian Community! You can do this if you set up a new permission scheme for all your projects that controls who can browse projects. This KB gives you a really good overview how permissions work in Jira. In the new permission scheme I would recommend that you use project roles, that way you can…

Okay, so you would have to create a screen that has the field resolution on it like this: Then in the workflow on the transition that moves the issue to Done, Edit the transition and add the screen you just created. Then on the post function, make sure that you do not have one that sets the resolution field.

Hi @Andrea S, Welcome to Atlassian Community! The resolution field is a special one, and you can only edit it if you add it to a screen, change it as part of a post function, or set it using an automation. So, do you want to change because it it wrong or do you want change it when moving your issue to the done status? 

Yes, any apps that needs to be added to Jira has to be done by an admin. 

Hi @Joshua Hultman, Welcome to Atlassian Community! Are you using Jira Data Center/Server or Jira Cloud? The easiest way to check it is to look at your URL, if it is https://<company>.atlassian.net you are on Cloud, if it does not contain atlassian.net then you are on Data Center/Server. The app that Hive has only works on…

@Munir Patel It should be possible as long as you have a REST API endpoint in Outlook for the manager. You can then use automation to get that information. We use Okta and can get that information via automation in JSM.

Yes, you can, for example I use Linked assets in JSM and have an automation that sets it based on the reporter like this: And you could create an automation for field value changed and select the custom field that is linked to Insight. What you cannot do is make updates to the Insight object directly in an automation, in…

Yes, the standalone Insight will eventually stop working, since you will not be able to renew the subscription for it. And yes, you need Jira Service Management Premium plan in order to get access to Insight in JSM.

Hi @Couraillon Theo, Welcome to Atlassian Community! Insight automations are now part of Automations (Project settings > Automations), just note that not all features that existed in the old Insight are not yet available. For example, if you want to update an object you have to do that via web request to the REST endpoint.

Those fields are added when you add the Time tracking field to the screens, so to remove them just go to the screen the issue type is using and remove time tracking.

Go to Settings > Issues > Custom fields. From here just click on Trashed and from here you can restore the field.

You just have to create a new field, have a look at this KB on how to configure approvals.

@Richard Way No, but you can keep an eye on JSDCLOUD-349 and also check out Atlassian Cloud changes that gets updated every week.

Request participants are your CC equivalent, since they can do the same thing as the reporter in the portal when they are added to the request. And yes, you could add a third field for your BCC users, and then use Automation or the notification scheme to notify them when the request changes.

@Joshua Keele what are you looking to do? Add the result from the query into a field?

This is being worked on, so in the near future you will be able to change the issue type, see JSDCLOUD-349 

Have you checked the box to allow other rules to trigger the one that transitions the linked Comp change?

Hi @[deleted], Welcome to Atlassian Community! Try this JQL: issuetype in ("Change Request", Story) AND (component != "WS10 Arbeitsvorrat" or component is EMPTY)