Mikael Sandberg Community Champion

{{issue.url.customer}} is the correct smart value to get the portal URL for the request.

Hi @Chandan Sharma, Welcome to Atlassian Community! Currently Assets is only available if you have a Jira Service Management Premium/Enterprise plan subscription, and if you do then you can use Assets object fields in Jira, but you would need a JSM license in order to access the schema via Assets. 

Hi @Mukadder AKPINAR, Welcome to Atlassian Community! The answer to all you questions are yes, JSM can do all of this. Some of the things you are looking for comes right out-of-the-box, and some things, like multiple approval steps, can be configured in the workflow. You may want to take a look at this JSM Quick start…

Hi @robert.tutic, Welcome to Atlassian Community! I have notified the Atlassian support team that is on here and they will get back to you within 2 business days to get this resolved.

Roles are not project specific, except for the ones that you define for Jira Product Discovery, and that is why you are seeing the service ones on a regular Jira space. Currently there is nothing that you can do about it other than ignore it.

AQL doesn't have the same option as JQL in automation were you can only include work items that have changed since the last time the rule ran. So if you are trying to cover gaps you have to add an additional lookup to see if a work item is linked to a specific asset before creating a new one.

Atlassian announced during Team 25 that Rovo is free if you have the Standard plan or higher. Please check out the Rovo FAQ. And no, Rovo is not in beta, it is now GA.

Hi @Chetan_N, Welcome to Atlassian Community! The short answer is no, you cannot have different names in different projects for the same field. 

In your person object, do you have a reference to the user's Atlassian account? You can do that by having an attribute that is of the user type.

Forms are intended to be used for users outside of the immediate team that is using the project, and currently there is no way of forcing everyone to use the form unless you use the proposed solution that @Matteo Vecchiato suggested.

Hi @Jovânio Sousa Morais Junior, Welcome to Atlassian Community! AWS has an active incident that as affecting apps like Jira, you can see the latest status by checking out https://jira-software.status.atlassian.com/ 

Hi @Unicom Assessoria, Welcome to Atlassian Community! AWS is having an active incident that is affecting applications like Trello. You can check the latest status by checking out https://trello.status.atlassian.com/. 

One thing to check is to see if the Resolution field is set on the tickets that are in the Closed status. 

Hi @Zrily Meisels, Welcome to Atlassian Community! AWS is having issues which is affecting Trello. You can check the status by going to https://trello.status.atlassian.com/ for the latest information. 

Is there a reason you are using @ mentioning in that field? Does it trigger a notification? If the answer is no then your option is to remove the @ mention and use the display name instead. What you are currently see is expected, any time you use the @ mention the value in the field is what you see, Jira just convert the…

Correct, yes. And you would have to contact the app vendor to see if they have it on their roadmap to open up admin settings to project admins.

Hi @Konstantinos Bilalis, Welcome to Atlassian Community! The short answer is that they can't, that page is only available for App admins, 

I would change the AQL to only search on objects that are 90 days out when the automation is run, that should prevent any duplications. Something like this: objectTypeId = 932 AND "Status" != "Closed" AND "Next Payment Date" = now(90d)

You are not missing anything, reusing transitions is currently not available in the new workflow editor. There is a suggestion that you can vote and follow, JRACLOUD-37296 

Hi @Tapia Quezada, Alberto, Welcome to Atlassian Community! The only way to remove those sprints is to remove them from the work items on your board. Your board and reports are all driven by the filter that is associated with the board, so if you have work items that are associated with sprints from other boards what you…

Hi @Salvatore Guglielmini, Welcome to Atlassian Community! You can change App access settings by going to admin.atlassian.com and then Apps > App access settings to change what users in an approved domain get access to when they first log in to your instance. 

@Rodney Dsouza _Atlassian Certified Expert_ Yes, the query is still working and it will return the user if it exists: https://your-instance.atlassian.net/rest/api/3/user/search?query=the.email@somewhere.com

What work item type did you test with? Based on your workflows the automation would only work if the work item type is task or subtask. The other default workflows do not have the Reopened status, so you would update the three workflows for incidents and service requests for the automation to work for those too.

Does the actual workflow have the reopened status? Based on the error message in the automation your workflow is either missing that status or there is no transition from Resolved to Reopened and that is why it is failing.

@Haripriya Shouldn't there be a link to the documentation for this action? Especially since this one only works for incidents? Currently the description is not mentioning anything about just working for incidents...

Hi @David Moorhouse, Welcome to Atlassian Community! You probably ended up here because your company is using an Atlassian product. This community is mainly made up of Atlassian customers and as such we do not have insight to other customers instances. I would recommend that you contact your IT department and they should…

Hi @Teresa Ferbet, Welcome to Atlassian Community! Linking work items is the way to go. When you say moving both items across the board, are you looking for a way of when you change the status of the user story to also set the same status for the linked task? If so then this can easily be done by using automation. Same…

I just tested and it looks like the new Send direct message on Slack isn't working correctly. I would suggest that you contact Atlassian support and have them look into it. My test automation was able to send a message using the Send Slack message component, and if you use that one you can send DMs as long as you know the…

Hi @Jakub Filo, Welcome to Atlassian Community! When you are sending the DM, are you using the user's Slack Member Id? 

If you are using a company-managed project you can limit the listed users by changing permission scheme so that Browse project and Assignable users are limited to a specific group or project role.