Mikael Sandberg Community Champion

No nothing else looks odd, I just know that some endpoints are particular when it comes to the headers, for example there are Confluence endpoints that expect Content-Type instead of content-type even though headers should not be case sensitive.

And the reason I am using two variables is because for some reason the text conversion is not working when doing it directly on lookupObjects on our environment.

You could simplify this, this is how I do it for a custom field that sets approvers based on what we have in Assets. The value you get from Assets is an array, so in order to set the custom field you need to replace the commas and the brackets. The way I do it is assign the output from lookupObjects to a variable and then…

You cannot add IF/ELSE condition within a branch, at least not yet. What type of branch are you using?

You may want to to check the headers you are sending, based on the documentation the groupuserpicker is expecting Accept: application/json, not Content-Type.

What type of space are you using? If you click on Spaces > Manage spaces it will tell you what type it is. Based on your description it sounds like the space you are using it is a team-managed space, and in those you cannot use "global" workflows, you have to change the workflow by going to the board in that space.

Hi @Britt Platte, Welcome to Atlassian Community! The ticket # you included above is to your internal JSM instance, not Atlassian. This community is mainly made up of Atlassian customers, and as such we do not have access to other customers instances. And without including any information like the error message or…

All in all I have ~30 automations on the JSM side, most of them do specific tasks like adding the banner to the internal page, and then I have a couple that acts as dispatchers and calling the specific automations based on what is needed.

So the automation in Confluence is making a web request to an automation in JSM that creates the ticket and adds information about the page, like the title, page Id. I also have a Rovo agent that generates a summary and keywords that is added to the ticket. Then it is up to the user to fill out who should approve, and once…

Hi @Tyler Ford, Welcome to Atlassian Community! I have used Comala Document Control and Comala Publishing in the past for this. Currently I have created our own process were you from within Confluence can start the review process, this will create a ticket in JSM, and once approved automations will copy the page to an…

In order to edit an object you need to create a global automation, then you can use the AQL branch to lookup the object and then use the edit object to set the attribute you want to update.

In order to use organizations you created under the App settings you first have to import/add them to the space. You do this by going to Customers > Organizations and click on Add organizations. This should allow you to select existing ones.

Hi @Андрей Орлов, Welcome to Atlassian Community! The short answer is no, you will not be able to purchase Data Center licenses after March 30, 2026 at 23:59 PST, as outlined in the Data Center EOL FAQ 

Hi @Max Puccio, Welcome to Atlassian Community! Please contact Atlassian support and the billing team by selecting Billing, payments, and pricing on the contact form and that team should be able to help you.

To add to @Mohamed Benziane answer, when using a service account you also have to use a different URL, you have to the Platform API Gateway URLs beginning with api.atlassian.com. Please see this KB for more information.

My previous job had both, and the only reason we had Sharepoint was because Finance used it to store files in it that they needed. Everything else was in Confluence, with a few exceptions like customer facing documentation that was stored in a different system. 

This should be fairly straight forward, all you need it use the smart value for the request type when you set the custom field on the business space ticket. The smart value is either {{issue.Request Type}} or {{issue.Customer Request Type}} dependent on when you first started using JSM.

Hi @Praveen Rapol, Welcome to Atlassian Community! This community is made up of mainly Atlassian customers and as such we do not have access to other customers instances. You need to contact your IT Helpdesk and they should be able to get you in touch with the right person that can help you with this. Note that I removed…

It's because the minimum number of users you can have when subscribing to either standard or premium is 5, as outlined in this FAQ.

Yes, there are two levels above the free one that you pay for. Have a look at the pricing page for Bitbucket for more information.

Hi @Nick Daniele, Welcome to Atlassian Community! In your automation, are you cloning the original ticket or are you creating a new work item? The request type cannot be set as part of creating a new work item, so what you have to do once the item is create is to add a branch in your automation that sets the request type…

Hi @Amy Rains , Welcome to Atlassian Community! You would have to contact your IT Helpdesk to get help with access. This is a forum made up of mainly Atlassian customers and as such we do not have access to other customers instances.

If you go into the work item detail view, do you see the resolution next to the status on the right-hand side? If not and you have a screen that is setting the resolution you should look and see if your workflow is clearing the resolution field or if you have an automation that is clearing it.

Hi @Mohsin Khan Welcome to Atlassian Community! Automations run after an action happens to the work item, and would not be able to prevent your epic to transition to done if child issues are still open. You would need an app from the Marketplace that extends the rules, one example is JMWE that has a rule that would allow…

The short answer is no, you cannot change the scope after the token is created. Currently your only option is to create a new token with the scopes needed.

Hi @Raja Muhammad Tahir Qaiser, Welcome to Atlassian Community! I have notified the support team from Atlassian that is on here and they will reach out to you within 2 business days to get this resolved. 

You would have to do the same thing as for a regular user, assign a license to the service account, add them to the right groups, and give them project permissions. If you are only using the account for automations and/or API calls you may want to consider using an Atlassian service account instead, they don't require a…

When you are using a service account you have to use a different URL than what the documentation is showing. These are the URLs that you have to use: * Jira apps: <a href="https://api.atlassian.com/ex/jira/%7Bcloudid%7D/%7Bapi" target="_blank" rel="nofollow noopener…

You have a couple of options, one is to use a Marketplace app that allows you to take external data and show that in a drop down field. I have used Elements Connect in the passed. Your other option would be to update the field via the API, but that can be complicated if your data is changing often.

Hi @Tapio Lakkinen, Welcome to Atlassian Community! A bit more information would be needed in order to answer your question, but based on the current one, automations are running after you do something to a work item, so notifying that at missing required field is not possible unless you "hard code" the field in the…