Tarun Sapra Community Champion

Please accept or upvote an answer. thanks.

The issue object is already available in the script runner execution context issue.getAssigneeUser().getDisplayName() Should get you the assignee's display name and for the URL you can easily construct that again in code "https://jira.mydomain.com"+"browse" + issue.getKey() Since "issue" object is present implicitly thus…

JIRA Service desk is awesome but one big pain issue that exists is the fact that - "Note: JIRA Service Desk is a plugin for JIRA. The JIRA Service Desk license type and user count must match that of the JIRA license it is being used with. For instance, a 25 User Commercial JIRA license will require a 25 User Commercial…

Why not JIRA Service Desk??? https://www.atlassian.com/software/jira/service-desk

The "Ready for testing" status should be the "Right-most" column on your scrum board and when the issue is moved to "ready for testing" the resolution should be set.

His Question is something different from your answer, he wants all issues with version greater than previous released version

In the global permissions of JIRA, who can log on to jira, i guess people who are part of jira-users group can log-on to jira, is the user part of the jira-users group?

Do these two things 1) In the Admin section of user directories in jira , test the user crendetials 2) Share the logs as well.

Are you using crowd or jira for user mgmt?

"Switch User" script in the script runner. 

No you can't do this on server version of JIRA - https://jira.atlassian.com/browse/JRA-2134 But if you have script runner plugin installed then it's possible as it has a built in script for doing the same.

The Adaptavist script runner isn't stand alone as far I know, but by python script I meant to have a stand alone script which will the the work for you. But yeah, you can user the script runner to have the groovy script in the post-function of the workflow of an issue. And for that issue have two fields , one having…

Please see here - https://github.com/m4ce/crowd-api-python you can retrieve the details of a user and add his groups to a list and then map these groups to the new user. 

Hi Darren, Currently, it's an open request - https://jira.atlassian.com/browse/CONF-22297 But I implemented something similar using a python script, which takes existing username and new username as input and adds the new user to all the groups same as the existing users. Crowd/JIRA have REST Apis thus it's easy to…

If it's single select list, then you need to supply only 1 value , like issue.update(fields={'customfield_10100': {'value':'Two'}}) But in your code you are giving two values "8" and "9" , why is that, is it multi-select ?

Currently this is not supported by JIRA, here' an open ticket - https://jira.atlassian.com/browse/JRA-7020 You can use a paid plugin to incorporate this feature in your JIRA - https://marketplace.atlassian.com/plugins/ca.nuum.gaia/server/overview 

thanks, i think this should do the trick -https://jamieechlin.atlassian.net/wiki/display/GRV/Built-In+Scripts#Built-InScripts-CopyCustomFieldValues

For high level tracking across multiple projects, I will suggest JIRA portfolio. For project Type, it's "Software" if most of the team are Software teams that would be using JIRA.

Ok, I have found a much better way to implement this functionality, in the script runner plugin there is a "built-in" script feature which would run on certain set of issues returned as result by a JQL, instead of writing a dedicated groovy script I have decided to use Escalation service to close all the linkedIssue of a…

HI Geert, Thanks for updating, I avoid writing custom scripts as external groovy files since things can get messed up quickly in lasrge JIRA instances and only in the new version of script runner I can write custom-scripts in the post-function itself, Thus right now I am exploring the possibility of firing a custom event…

HI Geert, so as the final solution you used your custom script or tweaked the built-in script?

Another easier way of doing this is to have a "Loopback" transition, i.e. in the workflow create a transition called "Create Sub-Task" and the post-function of that transition should create a sub-task and thus it would appear as a simple button on the view issue screen.

Another easier way of doing this is to have a "Loopback" transition, i.e. in the workflow create a transition called "Create Sub-Task" and the post-function of that transition should create a sub-task and thus it would appear as a simple button on the view issue screen.

Hello Alexey, To add a create-subtask button on the screen you would need to write a plugin, please see here - https://answers.atlassian.com/questions/276940/how-can-i-add-a-create-subtask-button-on-a-view-issue-screen

Hello @Jesper Eneberg To get the "maximum number of users" of the current license for JIRA, you can use the following KB article to query a plugin which would have the same maximum user license as JIRA. https://confluence.atlassian.com/jirakb/how-to-access-upm-rest-api-for-license-details-777021716.html

Indeed, I just noticed that as well, ALM Subversion has a really nice feature - Subversion JQL, but there are also strong chances that good plugins become paid quite quickly. 

You can install this free add-on https://marketplace.atlassian.com/plugins/com.atlassian.jira.plugin.ext.subversion/server/overview?_ga=1.98127895.98182588.1485420205 and here is the step by step guide https://confluence.atlassian.com/jira064/integrating-jira-with-subversion-720412771.html

IssueType is a built-in field thus I won't recommend changing it instead why not have a issueType called "Business" or "Business Type" , currently in JIRA you can't rename system fields like issueTypes - https://jira.atlassian.com/browse/JRA-21293…

Put the (Double) type casting where the aggregation is taking place. which plugin are you using for this functionality?

If you are using script runner for, make sure you use "Double" type