Mikael Sandberg Community Champion

The short answer is that you can't, the only thing you can do is set the component to wait until it gets a 200 response back and continue even if the response is not 200. What you could do is add an if/else component to check the returned status, and then if the API call allow it check the status of the request.

Due to the amount of options you want to add I would recommend using Assets and an Asset object custom field. It also makes it easier to maintain.

Hi @scotthanks, Welcome to Atlassian Community! Pull requests are not consuming space, but your commits are. There are different ways of rewriting the repository history, have a look at this guide from Atlassian, and this blog post on how to remove old commits.

Hi @Patrick Dooley, Welcome to Atlassian Community! The field name you are looking for is issuetype, the screenshot you included is from DC and there the field is shortened to Type. So, your query would look like this: issuetype = Test 

The short answer is that you cannot do that in a team-managed space. TMS only have one screen/layout and you cannot add additional ones. This can only be accomplished in a company-managed space were you can associate a transition with a screen.

Last year you were able to plan your sessions on the website and that carried over to the app, and that was opened up about a month before Team if my memory serves me correctly.

The app usually becomes available a week or two before Team, so I would expect it will be available end of April for this year's Team.

The IF/ELSE is under IF: Add a condition, once you click on that you should see it

Hi RC_Riley@rush.edu, Welcome to Atlassian Community! This community is mainly made up of Atlassian customers and as such we do not have access to other customers instances. You should contact your IT Helpdesk and they should be able to help you. 

Since it has been announced that data center is being sunsetted I would not expect this would come to fruition. Confluence Cloud can do this via automation, it has a branch for inactive pages that can be used to do this.

Check out this KB for more information about the limitations to free subscription.

Once an instance is deactivated Atlassian retains the data for another 120 days after the deactivation. So you would be way past being able to get that restored unfortunately.

Hi @sanaz_sadeghin Atlassian deactivate sites after a period of inactivity, usually after 90 days, and then the data is retained for another 60 days before the site is deleted. So that is why you after 2 years cannot access your site. Have a look at this KB for more information. 

Okay, as I assumed the way you have configured your rule is that it will never reach label B because it will not get past the condition for label A. As @John Funk mentioned, you have to use IF/ELSE in order to do that, something like this:

Hi @Erika Reategui, It is always better to include a screenshot of your automation so that we can see what it looks like, it makes the answer much better. Assuming that you are using if conditions in your automation I would say that the reason your automation never triggers on label B is that it never gets past the if…

Customer Service Management is a separate app and is included in the Service Collection, it is not automatically included in your JSM subscription.

Form answers from checkboxes comes back as an array, so your condition in the if component should use the contains instead of equal.

Okay, so based on the audit log it could be that your work item is not complete when the work item is created. You could either add a delay or change the automation to trigger on when the form is submitted and check the form answer instead by giving the field a key in the form (select the field and then scroll down to the…

Hi @Chad Henderson, Welcome to Atlassian Community! When you have an automation question it is always better to include a screenshot if the automation and the audit log so that we can see what you have tried so far. Without that information I can only give you a generic answer. This should be easy to do if you trigger your…

That all depends on the third-party app, in some cases an admin has to do the initial connection between Jira and the app, in order cases it will just create an API token and connect that way. But from an Atlassian standpoint there is nothing you can do on the admin side to set that up or approve/deny it.

Yes, that is only for Marketplace apps. Third-party apps that the user installed/granted access to is under Insights > API token activity, since the user is granting the app to impersonate them and that is done via APIs.

Hi @Taylor Huston, Welcome to Atlassian Community! The app interest can be found under admin.atlassian.com > Apps > User requests and under the User interests tab. Here is a KB that gives you more information about the process.

Hi @Pim Schrama CAt, Welcome to Atlassian Community! Analytics is currently only available for a page, live doc, or blog post. You cannot get analytics for a calendar. Please see this KB for more information.

The options shown in the dropdown for issue type is based on the issue types associated with the same workflow as the current issue type, it is not based on the hierarchy that you have defined. If you want to limit the options you would have to create a new workflow and associate the issue types that you want to be…

Hi @Gabriel Mota Welcome to Atlassian Community! This is a question for Atlassian Support and you should contact them via their contact form. This community is mainly made up of Atlassian Customers and as such we do not have access to other customers instances.

When you mentioned the jingle that plays when you walk in, it reminded me of my favorite store in Japan, Bic Camera (I worked in Japan for about 6 months). They have a specific jingle too when you walk in, and you can get almost everything there. Another family favorite is Costco as other have mentioned.

Hi @Si Scott Welcome to Atlassian Community! Yes, you can do this with automation. One option is to trigger on when the sprint is created to create both your stories and linked subtasks. Or you can trigger on when the sprint is set in the story, The first one is pretty straight forward, the second option would require a…

It would help if you included a screenshot of your automation, so my answer will be based on an assumption that you are using the if condition instead of if/else. If that is the case then it makes sense why the automation only works for Team A, because if you select Team B and using multiple if conditions it will stop on…

Hi @Michelle Medlin, Welcome to Atlassian Community! This community is mainly made up of Atlassian customers and as such we do not have access to other customers instances. Your best option is to contact your IT Helpdesk and they should be able to help you get access. 

Hi @iperamuna, Welcome to Atlassian Community! I have notified the Atlassian Support team and they will reach out to you within 2 business days to get this resolved.