Mikael Sandberg Community Champion

Hi @Jessica Wagner, Welcome to Atlassian Community! In a work management project the sub tasks to a work item are listed within the work item card like this: And unlike a software project the sub task cannot be moving separately on the board, it will aways follow the parent work item. 

Developer is a role in Jira, not in JSM. Anyone that has a Jira license and are added to the Service Desk Team role will be a collaborator and they will have access to view and add internal comments to tickets.

In order to create sub tasks the user would need at least a Jira license and be added as a collaborator in the JSM project. Sub tasks cannot be created from the portal, it can only be done from within JSM/Jira.

Hi @Christophe Le Coent ELCA , Welcome to Atlassian Community! I assume that you are using the X-Automation-Webhook-Token header to send the secret, correct? If you look at the audit log for the automation, does it indicate that the web request happened? Have you tried and checked the checkbox to delay the execution of…

What exactly are you trying to do? Are you saying you want to prevent someone from creating a work item in a project based on the returned value from a API call? If that is the case then the answer is no, that cannot be done since automations are executed after something happens, like create work item.

Hi @victorps , Welcome to Atlassian Community! The Atlassian support team that is on her has been notified and they will reach out to you within 2 business days to get this resolved.

This is something that needs to be asked internally, if the person that made the decision is no longer with the company or no one can explain why then I would consider changing it back to use story points. You could aways use automation to copy the value over from you custom field to story points and then let every one…

I think the Proforma API endpoints are going away and that is why you are getting the 404 error. I haven't seen an announcement about it yet, but recently there were an action added to automations for changing form status that you can now use to set the status.

So this is more of a question for your Jira admin on why it was decided to have a custom field for story points instead of using the built in one. I for one would have recommended against it since you loose features that comes built in when using story points, like the roll up. But there has to have been a reasoning behind…

Hi @Sophia Skinner Welcome to Atlassian Community! In order to add a new work item type to a project you need to add it to the work item type scheme that the project is associated with. You can do this by going to Project settings > Work items > Types and then up in the right-hand corner click Actions > Edit issue types.…

Okay, so at the moment those does not work in the new editor, the link macro do not have the advanced tab.

Hi @Beth Power, Welcome to Atlassian Community! You can do this by going to Project settings > Request management > Request types and locate the request type you want to change. Then go to work item view and move the field from Description fields to Context fields. Anything under Context fields will be shown on the right.

Currently the shortcuts can be links to other pages/spaces or you can use a URL, for example https://www.atlassian.com/

Hi @Stacie Bacon, Welcome to Atlassian Community! Yes, shortcut links should work for anyone that have access to the space you are creating them in. When you say you can't use them what do you mean? Do you not see the Shortcuts menu option? 

Hi @Admin Omar Olmos, Welcome to Atlassian Community! Is the Point of Contact field a user picker field? In order to set the request participant field via automation you need to know the Atlassian Id for the user that you want to set unless you pick from the list presented in the step.

Hi @Valérie GOMBERT, Welcome to Atlassian Community! The reason the changes are happing on the triggering work item is because the focus is on that, even when you use the "For current work item" branch. Instead you have to use the "For: Most recently created work item", that way the focus will be shifted to the work item…

Yes, that is possible and you can use smart value compare to do it. The returned result can be accessed using {{webResponse}} and you can then use the dot notation in order to get the value. You can have a look at this article that I wrote about incoming webbhook and using smart values.

And to add to @John Funk answer, when you are calling the webhook, are you sending data as a payload? Because you are using {{webhookData.sprint.id}} your payload should look something like this: { "sprint": { "id": "<sprintId>" } } But if you are only sending the sprint Id then you could simplify the payload. Have a look…

What you see is expected, the Virtual Agent does not currently work with widgets. It is only available for Slack/Team and the Portal.

Currently activating Rovo is on the instance level, you cannot control which projects it should/should not be activated for. But Rovo does respect the permissions a user has, so if your project is limited to specific users then users that do not have access to the project will not see results from that limited project.

It is possible, but only if the users you want to add have a Jira license. They have to have a Jira license in order to be able to view and add internal comments on tickets. You can read more about collaborators in this KB.

Hi @Mark, Welcome to Atlassian Community! You can do this by setting the attribute as a reference to other object schemas, for example with your laptop example the model would be a reference to the model object schema. 

Hi @j-alexis, Welcome to Atlassian Community! If you create an automation that triggers manually you can trigger it from a work item by clicking on Actions and it will be listed there. You can also set it up so that the user has to enter data before the automation runs. 

Yes, that is now possible. If you click on your avatar up in the right-hand corner and select Settings it will take you to the page where you can link accounts. Also check out this article that announced this setting.

Hi @Loucas Stylianou Welcome to Atlassian Community! You may want to post your question in the developer community or contact Atlassian support. Atlassian has done some maintenance to Assets that cause some issues in Automations, this could be a similar case. Regarding last, that has to do with pagination, but I know in…

It is possible, but you would need an app from the Marketplace in order to do it. It looks like Elements Overview can do this, but there might be other apps that show it on the portal as well.

If you look all the way at the top, right next to where it says Search Assets you should see the + Create button and that would allow you to create new objects.

Hi @Joan Parayno, Welcome to Atlassian Community! There is currently an active incident regarding Trello, you can find more information here, https://trello.status.atlassian.com/ 

Hi @Kathryn E_ Stine, Welcome to Atlassian Community! There is an active incident going on for Trello right now, you can check https://trello.status.atlassian.com/ for more information. 

Hi @Angela Arnold, There is an active incident concerning Trello right now, you can check https://trello.status.atlassian.com/ for the latest update.