Mikael Sandberg Community Champion

Hi @Anna Bagirova, Welcome to Atlassian Community! It sounds like you have a validator in the workflow that you are using that requires values for fix version and release note. If that should not be there then your admins have to update the workflow, or create a new workflow for BSA issues if the current workflow is shared…

I did a search in JAC but couldn't find an existing request for it.

Hi @Chris Ranero, Welcome to Atlassian Community! For the create screen you need to go into the screen that is being used for that issue type to change the order. Go to Project settings > Screens and from here you should be able to change the order or your fields. 

The answer to this question is similar to your other one here. If you go to the Automation library you will find this rule, all you have to do is tweak it to fit your use case. This rule would only move the parent issue if all subtasks are in the done status. I one subtask is not in that status, the automation will not do…

You need to change your branch to be the one For Epic (parent) that you can find if you go to the Automation library.

Yes, because JQL is currently the only option you have to find the epics linked to the initiative. Until parent() is replacing Epic Link and Parent link your first JQL would look something like this to get the epics related to your initiative: "Parent Link" = {{issue.key}} Since you cannot have a branch within the branch I…

Currently you cannot add attachments to a Form, that is something that Atlassian is working on and according to the public roadmap you should see this coming soon, it's scheduled for Q4 2022.

You can do this using automation that triggers on when that field is updated on the initiative, and then use the branch function to copy it to its related issues.

It can be done within JWM by using the Category field. I have a couple of JWM projects that does this, one of them is for customer requests that are then categorized based on what part of our platform it belongs to.

Yes, you would store your customer information in Assets, and add as many attributes that you want to them, and then when they create a request, have a separate customer field that is populated with the information you want to make available on the request. This would be done using automation that match the reporter to…

Yes, you could create a table in Confluence for it, but it would be a manual process to get that data since you would have to go to Confluence to look it up. If you want to do it with an Atlassian app your option is to upgrade to premium subscription which gives you access to Assets (formerly known as Insight) which can be…

Hi @Danna Levav, Welcome to Atlassian Community! Not from within JSM, you would have to add that information somewhere else. Either by upgrading to premium to get access to Assets, or use a CRM app that integrates with JSM. There are a couple in the Marketplace that allow you to do this. 

Hi @Peter Baxter, Welcome to Atlassian Community! I would recommend that they convert the subtask to a task/story and then use the link split from, just like you are thinking.

The switchover will happen automatically, you just have to follow the guide above to make sure you do not have issues that are not following the default hierarchy, if you do and do not take action those relations will not be preserved. The switchover will be based on the hierarchy that you have defined in your instance.

This is a known issue, I ran into this about a year ago and Support verified it. The workaround until the Automation team fixes it is to use a JQL instead to get the request type. I also noticed from my own testing that if you create a dummy request that would also allow you to see all other request types.

Is the Confluence link added as a web link or do you have a custom field for it? If it is just a web link you cannot add a column for it, that would only work if it is a custom field.

Hi @Brad Johnson, Welcome to Atlassian Community! Correct, team-managed JSM projects does not allow you to change the status via API. When Atlassian changed Jira Service Desk to Jira Service Management they also removed the option to create team-managed JSM projects, so you could create a new JSM project, migrate to that…

The built-in reports in JSM could do this, you just have to use the Filter by specific issues instead of the JQL from SLA goal. In the filter you can add that specific customer, something similar to this one that we have for our different tiers:

It does support it, but on Cloud you have to use markdown text to format the message. This link shows all the formatting that you can do, https://jira.atlassian.com/secure/WikiRendererHelpAction.jspa?section=all

@Ella Pestine My guess is no, especially since it used to be a separate app before.

Yes, it will behave similar to how Parent is currently working if you are on Premium and have a hierarchy above epics. It is not limited to a single project, parent and children can be in different projects.

@Carl Dichter This change will not affect the ability to link to a parent in a different project, every thing should stay the same as it is right now.

Yes, it is a team-managed thing, they don't have access to that context menu like company-managed projects do.

If you click in the Search up in the right-hand corner you can access Confluence advanced search and from here you can specify the users you want to search on and other options.

Have a look at this KB regarding Insight, or Assets as it is now being called. Basically what you have to do is create a new custom field of the type Insight object, configure it to be linked to a object schema and then just add it to the screens you want. I use it for not only assets, but for dropdown fields that have…

Yes, that is possible and can be done using automation. The automation would look something like this one that copies the fix version from the epic to the newly created issue if it hasn't been set already:

What you could do is disable the customer notification and instead use an Automation to send that message. Automation can access all the comments via the smart value {{issue.comments}} that you can use in the email response. This should return all the comments in the request: {{#issue.comments}} Comment by:…

It is possible, and what you are seeing when pulling the data for the issue is the reference to the Asset object (Insight is changing name to Assets). So what you have to do is use the endpoint to get the Asset object in order to get all the attributes.

You should have received an email regarding these changes and that email also included this guide to help you determine which issues that may be affected by the change and steps to maintain this data.

Hi @Patrick White, Welcome to Atlassian Community! The short answer is that upgrading to Premium will not affect your existing boards and roadmaps, the only difference would be that you get access to new features.