Mikael Sandberg Community Champion

Also take a look at this KB to learn more about how to use forms in JSM.

When you build your form you have an option to link the form field to a Jira field, like I did in this form Any changes to the description field on the form would also be reflected in the Jira description field and vice versa (as long as the form is not in a submitted status).

Correct, if you link the Form field to a Jira field you would need a second field and use the hidden section that I mentioned below and link that form field that is shown when Other is selected and then link that field to a Jira field.

It cannot be done using the request form, but you can add use forms to do this, it has an option to add Others to the list of choices, it looks something like this: Or you could add a hidden section that is shown if Other is selected to show a paragraph field when Other is selected.

The short answer is no, the Subtask summary is a team-managed space specific functionality. In a company-managed space you will see the sub tasks as shown in your picture above, and if you go into the parent you will see all sub tasks listed in its own section similar to linked items.

Have you checked to see if something happened to your JSM license?

Check your workflow to see if something changed there, make sure there are no restrictions on the transition. Also check that you have the service desk role in the project and that the permission scheme to make sure you have the right permission.

Have a look at this KB that describe what permissions are needed to have Jira users as collaborators in JSM.

Customer notifications are limited in what you can include, and custom fields cannot be included. Your option is to use an automation instead that sends the email notification and turn off the built-in customer notification.

Maybe try using an Atlassian service account instead of your personal account and API token? Note that if you use a service account the URL you use changes, for Jira it would look something like this: https://api.atlassian.com/ex/jira/{cloudId}/rest/api/3/project/{project_key}

I have notified the support team that is on here and they will reach out to you within 2 business days regarding this.

Hi @David Abraham, I have notified the support team that is on here and they will reach out to you within 2 business days to get this sorted. They can create the support request for you.

Correct, as a space admin you can only add pre-existing fields that your Jira admin has created. Space specific fields is not a thing in company-managed projects, it is only in team-managed projects that a space admin can add space specific fields.

Hi @Brittany Tran, Welcome to Atlassian Community! As a space admin you only have the option to add existing fields to your project, you cannot create new fields, in order to do that you need Jira admin permissions. 

Hi @suneel_babu, Welcome to Atlassian Community! You can do this if you use Assets, then you can create dependent fields and use Filter work item scope that was introduced a couple of years ago.

Hi @Nishant Singh, Welcome to Atlassian Community! When you sign up for the free tier you accept Atlassian's terms, and part of that is that your instance has to be active in order to prevent it from being deactivated and data deletion. The deletion happens within 60 days from when the instance is deactivated, and you get…

GraphQL can do it, just keep in mind that the returned result is paginated with a max of 100 test cases, so if you have a lot of them you have to do it multiple times. I just cloned ~3200 test cases between spaces using it this week. Once you have the output from GraphQL you have to convert it to a JSON file that the Xray…

Hi @Savanah Sexton, Welcome to Atlassian Community! One thing to check is to see if there are any restrictions on the parent page your user is trying to move the page to. Even if they have access to the space there might be a restriction that prevents them to view the parent. 

{{transition}} is not a smart value that automations recognize, but there are a couple of options to know which transition was used. You could set a custom field with the name, you could create a custom event and then use {{eventType}}, or you could use a property via the API that you can access via {{issue.{property}}}.…

There is also a suggestion to add a secret store, AUTO-1365, for automation so that you only have to go to one place and update the token. Please vote and follow if you would like to see this implemented. 

You could use a service account for this, that way you do not rely on individual users. Service accounts do not count towards your license count and you get up to 5 accounts that you can configure the access for. Have a look at this KB article for more information.

Hi @kuliha, Welcome to Atlassian Community! I have notified the support team that is on here, the will reach out to you within 2 business days to resolve this. 

Hi @John Stephens, Welcome to Atlassian Community! That is coming from this Marketplace app, AssetIT, and in order to remove it you would have to uninstall the app from you instance in order to remove it from the portal.

Very helpful, you get a quick overview of how JSM and CSM works together, will definitely recommend this one internally.

Hi @Alla Tadevosyan, Welcome to Atlassian Community! Boards are controlled by a filter, so that is what I would look at first. Does the filter return those items that are in the backlog status? 

Hi @ghammer, Welcome to Atlassian Community! Your board is controlled by a filter, so you have two options, You can either change the filter to exclude Canceled statuses, or you can associate the Canceled status with the furtherest right column on the board. Both options will allow you to close the sprint once done.

No, a username and password option is not available, but you can use API tokens. Your authentication would then be your email address and the API token, have a look at https://developer.atlassian.com/cloud/bitbucket/rest/intro/#api-tokens for more information.

That is based on the work item type scheme your space is using. If you want to have story as an option then you have to add that to your scheme, or if you are using a team-managed project add it to the list of work items that the space has.

If you are using SLA for the response time you can start by looking at the Automation template, there is a flow called When a SLA breaches → send a Slack notification that you can use as a starting point.

Hi @Mamidipaka Pavan Kumar, Welcome to Atlassian Community! Jira doesn't have field level security, so you would either have separate screens for creating the work item and then have a circular status that only admins can access that shows a screen with the specific fields, or use a Marketplace app that can do field…