Comments
-
Are you sure that the group is called like this? All letters in the upper case?
-
I modified the script. Now it will show all permissions where the group granted a permission through a role. import com.atlassian.jira.component.ComponentAccessor import com.atlassian.jira.scheme.Scheme import com.atlassian.jira.project.Project import com.atlassian.jira.bc.projectroles.ProjectRoleService import…
-
Try to look at the Big Picture plugin. In my opionion this plugin imitates Microsoft Project most.
-
You can wirte a script to clone issue and links. You can find more info here https://community.atlassian.com/t5/Marketplace-Apps-questions/Script-Runner-Example-for-Clone-issue-post-function/qaq-p/360406
-
It is not possible out of the box
-
What do you mean to "track"?
-
JQL returns only issues. You can not return users. That is why you would need to use a report from a plugin. Or you can get info by a rest call to GET /rest/api/2/issue/{issueIdOrKey} with the changelog parameter. Then you can write an applicaton on js to represent you the required data.
-
You can find it in the History or Transitions tabs of an issue.
-
You need to use updateProject from ProjectManager class https://docs.atlassian.com/software/jira/docs/api/7.2.0/com/atlassian/jira/project/ProjectManager.html
-
You are right, it must be CommentManager:)
-
I had same problems, when I met the new UI :)
-
In the post function email you can just get all comments from the issue and send them: String comments = ""; ComponentAccessor.getAttachmentManager().getAttachments(issue). { comments += it.getBody() }
-
What plugin do you have for scripting? If you can write a groovy script in your plugin, you can just write def date = new Date()
-
You can create an issue with the + button on the left side panel, right below the magnifier button.
-
Yes, you are calling the script the right way. The output must be on the Log tab, but the tab is empty. The script will only show permissions, if the group directly is set in the project permission scheme. You you set a group for a role and then added to the role to the project permission scheme, then such a permission…
-
Такое происходит если у тебя в спринт на одной борде попадает такой же запрос как и на другой борде. У тебя не должно быть одних и тех же запросов на разных бордах. Это можешь фильтром доски определить.
-
It would show only going forward event. You need to have a look at what url is called on the export button and then add serlver-filter module into your plugin for the url. The module will intercept all calls to the url. When you intercept the call, you log the event with the required info.
-
You need to do it once for a project and then you can create a new project with shared configuration. In this case the new project will have the same schemes as the existing project. You can find more info here: https://confluence.atlassian.com/adminjiraserver070/defining-a-project-749382822.html
-
I am afraid, that you can not do it without an add-on like Power Scripts or ScriptRunner.
-
Не должно быть одинаковых запросов в двух спринтах.
-
could you provide a screeshot with the list of projects? Just one line. I do not need all the lines.
-
Have a look at the response message, which Jira returns. There will a detailed explanation of your error. Or install Rest Browser plugin and execute your rest method there. You will see the error.
-
You can use a script like this: import com.atlassian.jira.component.ComponentAccessor import com.atlassian.jira.scheme.Scheme import com.atlassian.jira.project.Project String groupName = "group name" def a = ComponentAccessor.getProjectManager().getProjectObjects().each{ project ->…
-
Kindly read the following article https://confluence.atlassian.com/adminjiraserver071/using-the-issue-collector-802592637.html
-
Yes, it would combine them. Ah, I see . you want to see them on separate graphs. I guess, it is not possible.
-
When you publish a workflow you will publish it for all issue types, for which the workflow has been defined. You can not publish it just for a single issue type. That is why you are asked to associate statuses for all issue types.
-
When you run the report you can choose to take issues from a project or a filter. You should create a filter, which selects issues from two projects, and run the report with the filter.
-
You can edit Jira user properties. You can read more info here: https://confluence.atlassian.com/cloud/add-data-to-users-for-advanced-functions-jira-applications-only-744721649.html
-
You would need a plugin for it like Power Scripts, Automation For Jira, ScriptRunner or Workflow Toolbox. Or you can develop your own plugin.
-
You can find more info here: https://confluence.atlassian.com/adminjiraserver071/migrating-jira-applications-to-another-server-802592269.html