Mikael Sandberg Community Champion

If you remove objectType from your query and only using Name, does that work? Normally the objectType has already been associated with the custom field so you do not have to add that in the IQL.

Currently there is no endpoint for creating API tokens, the only thing you can do is get and delete a token. Based on this suggestion, ID-6829, Atlassian does not intend to create an endpoint that would allow you to create API tokens via REST API. 

You need to use the condition component, and your automation would look something like this: This one is what I use for round robin assignment, but the concept is the same as for the automation you are looking for.

The short answer is it cannot be done. You have to make the change in each project, since request types are project specific. There is a suggestion to add request type scheme, JSDCLOUD-4276, that you can vote on and follow.

I don't, I did a quick search on https://jira.atlassian.com/ and couldn't find any suggestions for this, so you could always create one and add the business case for it.

Hi @joey_beekman, Welcome to Atlassian Community! Currently you cannot make the form only visible to certain users, the only thing you can do is mark it as internal (only visible to JSM agents in the project) or external (makes the form visible via the portal). 

Yes, that is possible, you just have to use the if/else condition. Please note that there is a limit on how many components (conditions, actions, etc) you can use in an automation, which is currently set to 64. So do not go overboard with components in a single automation.

So you could do this by having an automation that triggers when the Fix version field is updated, and then use a web request to Get version to get the release date and if it falls within x days send a notification to the team.

Hi @Rasika Vernekar, Welcome to Atlassian Community! You would need an app in order to do it, and the only available one at the moment is Floating Table of Contents for Confluence. There is a suggestion to add a macro for it that you can vote for, CONFCLOUD-72545

You can change the search template if you go to Settings > Issues > Custom fields, then click on the three-dot menu and select Edit details.

Your automation that sets the tier field would look something like this: What you would change is when the automation, the one above is what we are using, so just change the trigger to be when issue is transitioned to your escalated status.

The short answer is no, you cannot have multiple development branches defined in Bitbucket. Git only supports a single development branch.

Hi @Kevin Chadwick, Welcome to Atlassian Community! You can do this using automations. We do this in our IT project, we have 4 different tiers (this is a custom field that we have) and that field is updated based on the assignee. You could also do this based on project roles. So if the assignee belongs to the role…

Yes, it is possible, all you need is a REST API client in Perl and then use then access the endpoints you need. The permissions needed depends on what endpoint you are hitting. Here is a Jira wrapper and here is a collection of examples for Perl.

No, your issue is that you will run into performance issues when someone will try and use the field. I would consider using an external data source, or if you have access to Insight use that instead because the field values are populated when the user is typing in the field instead of having to wait for the list to first…

Hi @Sravan Muppavarapu, Welcome to Atlassian Community! You could use the REST API to do this and Scriptrunner should work too, but you should really consider it you want to add those 3000 plus options. The select field doesn't have a hard limit, but you will run into performance issues, see this question. Another option…

Have a look at this KB regarding the best practice on using the resolution field. You can do this by changing your workflow and add a post function on the transition that takes your issues to Rejected or Done that sets the resolution field.

Are you looking for information on how to make these changes or did you intend to contact your Jira admin to get these changes done? Atlassian Community users do not have access to customers instances, so we cannot help you make the changes, but if you are looking for information on how to make these changes that we can…

There is no function that would allow you to get all issues created on a specific day of the week for all time. You would have to string together multiple created > startOfWeek("xxx") AND created < startOfWeek("xxx") in that case, something like this: (created > startOfWeek("+1d") AND created < startOfWeek("+2d")…

Yes, you would need different approval fields for it, so in the case of application access I have a manager field and system owner approver. Then in the approval step you define which field is the source for the approval.

Yes, that is feasible. I have two approval statuses for application access requests, one is for their manager and the second one is for the system owner. There is no limit on how many approval statuses you have in the workflow.

Hi @Tanner.Johnson, Welcome to Atlassian Community! You could use Who's Looking for Jira Cloud for this, it shows you a list of users that currently have the issue opened, and based on the description it does not require a page refresh.

So I found an answer in this thread. It looks like there is a security threat in it and that is why it has been temporarily removed from the Marketplace.

Hi @Joe Harrington, Welcome to Atlassian Community! Team calendars are now part of Confluence Premium subscription, so you would have to upgrade your subscription in order to get access to it. You can find a comparison between the different plans here. 

Hmm, so you should be able to get to it if you go to Apps > Find new apps in Confluence, but since it not showing up when you search on it and the Marketplace listing is only showing versions it leads me to believe that the app has been discontinued. I haven't seen an announcement about it, so I have notified the Atlassian…

@Chad Jackson I no longer using Scriptrunner after I switched company and went all cloud. At my previous place we used Scriptrunner and validators to prevent issues to move forward unless specific conditions were met. We also used it to do post-function calculations to get the risk value based on what the user selected…

Hi @M0214104, This is easily done using automation and a custom field. The automation can update the story with the epic id when the story is linked to the epic. 

Ah, my brain was thinking faster than I was typing. The correct syntax would be created > startOfWeek("+1d") AND created < startOfWeek("+2d") This would give you issues that were created on Monday

In the project that you cannot plan tasks for, make sure that you have permissions to schedule issues if you are using a company-managed project.

A little bit more information is needed here, are you looking to include the description in the initial email that is sent out?