Mikael Sandberg Community Champion

When you say form, are you talking about the Request Form or the Form that allows you to add dynamic forms to the request? It if is the request form then all you would have to do is use that field in an automation to send the email. If it is Form then you would have to map that field to a Jira field and then do the same…

There isn't a smart value for the user that would get you the project role they belong to, so you have two options. You could either create a manual automation and only allow a specific group to run it or the other option would be in the automation use the web hook component to get the project role and then check if the…

When you enabled the resolution field, did you also add it to the create screen? If you add the resolution field to a screen the field will automatically become required, so the recommendation is that you should only add it to transition screens or set it automatically via post function when moving to a done status.

Forms are only available in JSM and JWM, you would only have access to forms in JSW if you had the app ProForma Forms before Atlassian acquired it.

No, the change would have been done by your Jira admins, this would not have been part of any changes from Atlassian. There is a new feature coming soon that would allow you to set priorities on the project level that would prevent you from affecting all projects when you change the default one.

Hi @Eric Blankenship, Welcome to Atlassian Community! It sounds like one of your Jira admins changed the default priority, when you change the default priority it will affect all projects. If you go to Settings > Issues > Priorities you can see which one is set to default and also change that.

Hi @Amina Begum, Welcome to Atlassian Community! Atlassian is aware of this and they are working on a fix for it so hopefully this will start working again soon. 

Hi @Maurice Huellein, Welcome to Atlassian Community! This is a known issue and Atlassian is working on a solution for it. 

The short answer is that most apps do not allow you do delete them from the side bar. Some apps allow you to enable them for specific projects, but in most cases that is not an option. The only way to remove them would be to uninstall the app.

In order to remove fields from a specific issue type can be done in a couple of ways. If the fields are optional then you can associate that issue type with new screens/screen scheme. The other option is to create a new field configuration and associate it to the issue type. In the field configuration you can hide fields,…

Try and remove .parent. from your smart values, {{issue.summary}} should give you the summary for the task that you just created since that is the branch you are on when creating the subtask.

There is a suggestion to add versioning, see CONFCLOUD-76694. I would suggest that you vote and follow it. 

If you go into your advanced form and then click on the Settings tab you should be able to associate it with the issue type. You should see something like this:

The short answer is no, a JWM project cannot show information from multiple project on the board. What you can do is create an overview of multiple JWM projects, that will give you the summary, calendar, and timeline view will all the JWM projects that you included.

Hi @Jimmy Kim, Welcome to Atlassian Community! Yes, tasks that are linked to a story can move individually. It is only sub-tasks that have to move as a whole with parent. 

The KB you found only applies to Atlassian Analytics, which is a Cloud only application. There is nothing equivalent in automation, so you would have to use math expressions in order to convert the date into a julian date.

The approver field should be like any other fields, just use the edit issue component in the automation to add them. It is not showing up as an option then you can always use the advanced option to update the field, something like this: { "update": { "customfield_12345": [{ "add": { "id":"<Atlassian Id>" } }] } } Note that…

Hi @John Lombardo, Welcome to Atlassian Community! If you look at the warning message it is expecting a user to be added to the Approver field, not the Approvers. So It looks like you have two or more fields for approvers. 

Correct, in order to turn on anonymous access to Confluence you have to be on at least the standard plan. 

Hi @Harry Poole, Welcome to Atlassian Community! The reason you are seeing a difference is that in your employers Jira instance you do not have a JSM license, or you have not been given agent access to the project, all you have s Jira access and that is why you are not seeing the queues or the knowledge base. 

The short answer is no, you cannot filter based on when the label was added. The workaround would be to have a date/time custom field that is updated when the specific label is added to the issue.

You can use the due date to do this, and then the automation would look something like this:

@Steve Lundy It does, the second paragraph spells it out: It does not fully delete your content, it just changes access to the page

The API endpoint that you are trying to use is only available on JSM Cloud, JSM Server/Data Center only has an endpoint to add customers, not get. Here is the API documentation for it, https://docs.atlassian.com/jira-servicedesk/REST/5.11.3/#servicedeskapi/servicedesk/{serviceDeskId}/customer

Yes, if you check the app listing it will have a link to their documentation which describe how to set up the integration.

If you are doing this in a dashboard then yes, it is possible to remove sub tasks. It all depends on how you configure the filter that you use in your gadget. Your JQL to not include sub tasks would look something like this: project = JRA AND issuetype != subtask

Did you happen to take a look at the Marketplace? There are a handful of apps that integrate SFDC with Jira, I use Connector for Salesforce & Jira and so far that has been working fine.

Okay, so the epic color is only displayed on issues that are associated with them. If you adding the issue color as a field to the card it will only show the text, not the actual color. A workaround would be to set up card colors under board settings and use the issue color in the query, that would change the boarder of…

Are the issues on your board associated with an epic? If they are then the epic and the color should be shown on the board, but if they are not linked to an epic there is no color.

You can learn more about smart values here.