Comments
-
Then you need to iterate over all users and find the required user. import com.atlassian.jira.component.ComponentAccessor import com.atlassian.jira.security.login.LoginManager def loginManager = ComponentAccessor.getComponent(LoginManager.class); ComponentAccessor.getUserManager().getAllUsers().each{ it-> if ("user display…
-
In this case you have to write a script yourself. First of all, epics, stories and tasks are connected by links. You can get all linked issues to an issue. You can find more info here: https://community.atlassian.com/t5/Jira-questions/Linking-Issues-in-jira-using-groovy/qaq-p/98301 Then you need to check the statuses of…
-
You can find a user by display name like this. The it varable contains the user. import com.atlassian.jira.component.ComponentAccessor import com.atlassian.jira.bc.user.search.UserSearchService import com.atlassian.jira.bc.user.search.UserSearchParams def userSearchService =…
-
No, you can not write like this. changeItems.getAt(i).get("field") returns the name of the field. You can log the changeItems varable and have a look at its structure. You should define your listener for the Update Issue event.
-
You need to create a post function plugin. Which would find the parent of the sub-task and set the fix version for the sub-task. https://developer.atlassian.com/server/jira/platform/creating-workflow-extensions/ You can use Power Scripts or ScriptRunner plugins. These plugins will make it easier for you to create such…
-
I guess, the only way to integrate VBA and Jira is the Jira's Rest Api. But I do not know how to call REST functions from VBA. I am not an expert on VBA.
-
First of all you need to define what is an active project. Secondly, you need to define what a project status is. But I think you need an add-on to get the required info. You can have a look at EazyBi or any other reporting plugins.
-
I think, you can not do it out of the box.
-
reporter = username
-
You would need to write your own plugin.
-
Kindly read my article. https://community.atlassian.com/t5/Jira-articles/Work-with-your-Jira-plugin-from-Adaptivist-ScriptRunner-or-how/ba-p/719050
-
You can not change the Issues in Epic panel. You should use an add-on like Issue Matrix.
-
If you have the ScriptRunner add-on and tasks are actually sub-tasks, then better use the built in function, called Transition parent when all subtasks are resolved https://scriptrunner.adaptavist.com/latest/jira/builtin-scripts.html#_transition_parent_when_all_subtasks_are_resolved If tasks are not subtasks then it will…
-
You can get what was changed with the following code: int i =0 while (i < changeItems?.size()) { log.error(changeItems.getAt(i).get("field")) i++; }
-
By the way I tested your script on Jira 7.7.0 and it worked fine
-
That is a strange behaviour. I do not think there are any problems with indexes. Because indexes store issue data. When you created a version it is not an issue data. It will become issue data only when you set this version for an issue.
-
Yes, that is because the users are coming from LDAP. I guess all your users belong to some group in LDAP. Add this group to the Service Desk groups in Applications -> Application Access and your users from LDAP will be Service Desk agents. This group does not need to be the default group.
-
If you provided a license key then it is sufficient
-
You should have a look at the logs what is going on.
-
Jira can be installed fine without internet connection. You need get the license key in your my.atlassian.com and install the key.
-
Do I understand correctly, that you have a post function, where you create a version? then you open another ticket and try to choose the created version and you have the error?
-
You need to add the required fields to the issue navigator with the Column button
-
Kindly have a look at how to transition an issue https://community.atlassian.com/t5/Marketplace-Apps-questions/Groovy-Script-for-Linked-Issue-Transition/qaq-p/17706 if you have ScriptRunner then there is a built in function Fast track transition issue…
-
If you have ScriptRunner plugin then you can use the built-in function Copy Project https://scriptrunner.adaptavist.com/latest/jira/builtin-scripts.html#_copy_project Or you can use Configuration Manager or Project Configurator plugins.
-
Do you use Issue Navigator to export your backlog? If so then choose Export Excel CSV (current fields):
-
Behaviour do work like this. If you click on a filed in the view issue screen then the edit issue screen will be opened. You can read about it here https://scriptrunner.adaptavist.com/latest/jira/behaviours-overview.html#_screens
-
You have no screen attached. I am out of ideas.
-
You should set assignee like this "fields": {"assignee": { "name": "homer" }} and you should add comments using POST /rest/api/2/issue/{issueIdOrKey}/comment
-
What do you mean by "we'd have to add the custom field to view each time"? You need to push the edit button and enter a value.
-
You can not change the behaviour. It is an internal Jira behaviour. You would need to write your own custom field plugin and return an empty string if the value is null.