Kristian Walker _Adaptavist_ Community Champion

Hi Bryan, I can confirm that if you have the ScriptRunner for Jira Cloud plugin in your instance, then this could help achieve this requirement. We gave an example script here that will bulk-flag issues returned by a JQL search. You could run this script as an Escalation Service in order to flag the subtasks which are open…

Hi David, I am glad this answer helped :) Regards, Kristian

Hi Sunilkumar, In Jira Cloud, Atlassian does not allow a default link type to be set or to have the default link type be the previously used link type on an issue as they do not provide these features. The link type which appears as the default is the one which appears alphabetically on the Issue Linking page. This means…

Hi David, Thank you for the update. I can confirm it is not possible to restrict the Move options shown above as Jira does not allow this. The only thing you can do is to stop users from seeing this move option by editing the Move Issues permission in the projects permisison scheme to not allow users permisison to move…

Hi Manasa, I would suggest that to create a view of all of the tasks that users have assigned to them by creating a Jira Dashboard that would display this information. To do this, I would advise creating a JQL search to see all tasks assigned to the current user that are not closed, with some JQL similar to issuetype =…

Hi IT Admin, I can confirm in Jira Cloud you can register a custom domain by following the steps Atlassian have documented here. Adding the domain is just adding a new URL to access the service desk and so should not affect any permissions inside of Jira, although it would be best to confirm this with the Atlassian support…

Hi Marcelo, To be able to assign user issues in an even manner, you would need to make sure you assign the issue to the next element in the array of user IDs each time. One way to do this would be to use a project property inside of Jira cloud, as you could then update this each time an issue is assigned with the element…

Hi David, I can confirm with ScriptRunner that for Jira Cloud it is possible to restrict issue types only on the Create screen currently with Behaviours, and the example here shows how to do this. Also, this documentation shows what fields behaviours support on the Create Screen and what fields it supports on the issue…

Hi Shmuel, I can confirm that the time tracking reports that Atlassian provide are limited, so using an add-on on this requirement will not be entirely possible. However, out-of-the-box in Jira Cloud you can use the Dashboard Gadgets Jira cloud provides, as documented here and the Time Since Issues Gadget and the Average…

Hi Yingi, I can confirm that if you use ScriptRunner for Jira Cloud then you can write a script to run as a script listener and automatically add or remove issue links when a script is updated or created using a Script Listener. Your script would need to check if the value of your required field had changed using the issue…

Hi Brandon, As Bobby mentioned, number fields are not yet supported. The only workaround is to call the .toString() method to return the value as a string and set this in a text custom field. Regards, Kristian

Hi Caoimhin, I can confirm that scripted fields cannot be triggered to update daily, but using ScriptRunner, you could use a Schedule to update a custom field with a calculated value at a defined interval. This means the field could be updated daily, such as 6 am, to ensure the value is always up-to-date in dashboards. I…

Hi Shivani, This can be done using ScriptRunner, and we have some examples of how to do this, which I have linked below. * Server / Data Center Example * Cloud Exampe I hope this helps. Regards, Kristian

Hi Ahmed, I am glad you got it working. Can you please mark mine and Trudy's answers as accepted to help show other users that this is a correct answer. Regards, Kristian

Hi Kai, I can confirm behaviours for Jira Cloud can restrict issue types on the create screen, and we have an example here that can help show how to do this. However, as the create screen shows all issue types by default, there is no way to restrict them based on a board, as Jira does not allow this. I hope this helps.…

Hi Benjamin, As ScriptRunner for Jira Cloud runs Groovy, you should use the replaceAll method as documented here. Using this, you would assign your string to a variable, and then you could call replace all on it using a regular expression to remove everything inside and including the brackets, as shown in the example here.…

Hi Benjamin, I am glad it helped. Could I please ask you to accept the answer to mark it as correct for other users to find? Regards, Kristian

Hi Ankush, ScriptRunner for Jira cloud can display custom HTML, CSS and Javascript, which means you could write some custom HTML hosted somewhere externally, such as CodePen as mentioned in the documentation here. This custom HTML CSS and Javascript would define the logic to create the button that you require and you would…

Hi Benjamin, I can confirm that to set a component, you can use the example located here. Using this, you will see that the components field needs to be an array where each element is an array which has the name and value of the component. This example can be run on the script console to see how it works and then moved…

Hi Heather, Thank you for your question. I can confirm thaty the ScriptRunner for Jira Cloud plugin could help to achieve your requirement. Using ScriptRunner you could a post function tp the transition that transitions the issue from the Ready Status to the In Progress status and have this create the issue and a link to…

Hi MM6161, You are welcome. Can I please ask you to accept the answer if it has helped to solve your requirement? Regards, Kristian

Hi Samayak, Thank you for your question. I can confirm that to add a pre-populated description with behaviours, you can use the example we have in the Script Libray here. You will then need to change the Atlassian document format for the format you want, and the easiest way to get this is to use the visual editor tool…

Hi, MM6161, This looks correct. One thing I would advise is referring to fields by Id instead of name in scripts, as if you have 2 fields with the same name inside your instance this will cause the field not to be found. I have just done a test adding a description to the assignee field to confirm this works on a transiton…

Hi MM6161, Unfortunately, adding text above a field in Jira is impossible. You can only add text below the field on any screen using either of the approaches mentioned above. Regards, Kristian

Hi MM6161, Are you using Jira Server/Data Center or Jira Cloud. Using built-in Jira, you can set a field description on the field configuration page and this will add in the text below the field that can be used to explain to a user how to use the field. If you are using Jira Server/Data Center then you can use the…

Hi Michal, Thank you for your question. I can confirm that scriptRunner for Jira Cloud now supports the radio buttons field and these have the key of com.atlassian.jira.plugin.system.customfieldtypes:radiobuttons. This means if you replace the key for select list fields in the example script with this key and map the…

Hi Ahmed, I can confirm that the Behaviours feature inside of Scriptrunner for Jira Cloud will be able to help with your requirements. An example script here shows how to restrict issue types to users in a specific project role. You can modify this to achieve your requirements by replacing the restrict issue type API calls…

Hi Trudy, I can confirm we have now released support on the issue view screen for the backlog view and board view as mentioned in our documentation page located here. Regards, Kristian

Hi Celina, Please can I confirm by release do you mean Versions, which are created under a project settings page? If so, you can call the Update Version rest API, which Atlassian provides using Scriptrunner to update a version and set its archived property to true. This API takes the ID of the version to be updated as a…

Hi Todd, This error means the Expression failed, as your syntax for the Jira Expression Framework provided by Atlassian which we use is invalid. Specifying the length of the checkbox makes the syntax correct and means that this is the only value selected. If you want any of the values in the field to match then I have…