Mikael Sandberg Community Champion

Hi @Nathan Rogowski, Besides @Trudy P Claspill suggestion and what you found that @Bill Sheboy posted, one option would be to use space properties. Properties can only be accessed via the API, so they are not exposed to regular users. For example, I am using page properties in Confluence to link the page to a review ticket…

Quick way of getting started with Jira, I like it!

Short answer is no, subtasks cannot have a subtask. The way you can associate a test to a subtask is to use link work items.

Great way to get a quick introduction to Confluence! Nice one!

You should submit a ticket to Atlassian Support, I ran into the same issue on the Confluence side. the API token works correctly if used in Postman, but via automation it returns a 401 error. This worked as of last Friday, so something has changed in Automations since then.

There is currently an active incident that are affecting multiple Atlassian apps. please check out https://status.atlassian.com/ for the latest updates.

There is currently an active incident that are affecting multiple Atlassian apps. please check out https://status.atlassian.com/ for the latest updates.

Here is how I would approach the solution for this, I would create a main automation that trigger when the label is set. This main automation would cover all 4 labels, and if any of them is set it will call a corresponding automation for each label that creates the tickets. This will help you stay within the 65 component…

You should be able to find your answers here, https://www.atlassian.com/trust/atlassian-intelligence. Data is transferred outside, but does follow existing Atlassian security practices. When using Rovo, data is transferred outside of the current site to third party LLM providers (e.g., OpenAI) in order to generate a…

Here is an article on how to do it via the API, https://community.atlassian.com/forums/Jira-articles/Change-Form-visibility-using-Automation-and-API/ba-p/2385306

@Kyle Elliott no I don't, I created that at my previous employer and don't have access to that instance anymore.

Here is another good KB on how to handle this, https://support.atlassian.com/jira/kb/add-update-remove-request-participants-using-automation-in-jsm-cloud/

In order to change the scope to be either multiple spaces of global you need to have Jira admin access. If you do not see a link to global automations when you go to rule details in the automation it means you do not have Jira admin. 

Opsgenie is no longer available as a separate app for new customers, new sales ended on June 4, 2025 and support will end on April 5, 2027. New customers should trial JSM, Operations is what is replacing Opsgenie.

You have a couple of options here, one being to use Smart Assignment & Rotations app that you can find in the Marketplace. Your other option would be to use an automation, but that can be hard to maintain if the rotations changes week to week. The alternative is to create an automation that relies on the Operations on-call…

You have two options to assign an asset to your employees. Will all employees have a license in your Atlassian instance (could be for any Atlassian app, as long as they are managed)? If so then you can use the user attribute and associate an asset that way. If only a subset of your employees will have a license then you…

The app that @Anthony Morais linked to can do this; if you are looking to create something yourself then have a look at this article, I created the solution with Operations on-call schedule before Smart assignments app were available. 

Does the user in question have a JSM license?

I have notified the Atlassian. support team that is on here and they will contact you within two business days to get this resolved.

Btw, the documentation for it is under Service Accounts, but the scoped domains applies to any scoped API token, and you can find the documentation here.

What domain are you using when accessing the endpoint? Scoped tokens have to use api.atlassian.com domain instead of yourdomain.atlassian.net, and for Jira the URL should look like this: https://api.atlassian.com/ex/jira/<cloudid>/<api>

If you are using the new workflow editor, all you have to do is click on the transition and you should see the option to make it available on the portal:

Please send this to abuse@atlassian.com and they will take action on it. Note that the team will not reply back.

There is an active incident, https://bitbucket.status.atlassian.com/.

Currently it is not possible to trigger an automation on when a web link is added. There is a suggestion for it that you can view and vote on, see AUTO-776. Also check out AUTO-1776, its for adding web links as smart values. 

The default customer notifications cannot be customized for each request type, in order to do that you would have to use automations instead and then disable the customer notification.

Teams at my previous job used whiteboards for snaking/issue planning instead of Lucidchart. Lately I have used it to document automations to give a quick overview how they are linked to each other. And by doing that you can also get a quick overview if you have multiple automations that triggers at the same time that could…

You should be able to do it via the API, Create page has a subtype that allows you to set the page to live.

Yes, you can create custom field contexts using the API, this is the end point, Create custom field context. I am not sure it you are able to set the AQL filtering section or not...

In order to achieve this you will have to set up a context for each project and then use filter scope in order to limit the object field to only show objects related to the specific project. It cannot be done with smart values.