Alexey Matveev Expert

Hello, Kindly make sure that these users are included in any group in the Application Access menu. Go to Jira Settings-> Applications -> Aplication access

Hello, User the LoginManager class. LoginManager loginManager = ComponentAccessor.getComponent(LoginManager.class); LoginInfo loginInfo = loginManager.getLoginInfo(String userName) log.error(loginInfo.getLastLoginTime() )

Use the "where is my field button" in the create screen to receive info, why the Time tracking field is absent.

Hello, I think you should add the project data to your json. And your json does not look correct. Have a look at an example of such a json here: https://docs.atlassian.com/software/jira/docs/api/REST/7.11.0/?_ga=2.24127550.504800534.1533537083-1659643416.1506407535#api/2/issue-createIssue

When you setup Approvals you choose, which transitions must be executed in case the issue is approved or rejected. In the end transitions, which you provided, will be execute. I think in your case it is the Start Progress transition.

Hello, Kindly read the following thread: https://community.atlassian.com/t5/Answers-Developer-Questions/Change-sprint-value-by-groovy-script/qaq-p/522895 There is an idea on how to work with sprints in groovy

Hello, Did you add the Time tracking field for the create issue screen?

Hello, You should use the search Rest Api. You can find more info here: https://developer.atlassian.com/cloud/jira/platform/rest/#api-api-2-search-get

Hello, You are right if a field is not configured for a project in the field context, then even if you add this field to a screen in this project, the field will not be visible. 

Hello, The Status field is a global entity. If is not a workflow entity. If you change a status name, the name will be changed in all workflows, where the status is used. If you want to have different names for a status in different workflows, you should create a separate status for each workflow.

Is this post function in the create issue tranistion? If so, is it last in the list of post functions? What are the errors? What does not work?

You should put it before the createIssueLink

It would be something like this: def linkMgr = ComponentAccessor.getIssueLinkManager(); def issueLink = linkMgr.getIssueLink(sourceIssue.getId(), destinationIssue.getId(), linkTypeID); if (issueLink != null) { linkMgr.removeIssueLink(issueLink, user); } The IssueLinkManager class is responsible for handling links. You can…

Hello, Each link has the outward and inward descriptions. Do you mean that you want to know the id of the inward description? If so, you do not need it. When you create a link between issues using createIssueLink, the first variable is the source issue(outward) and the second variable is the destination issue (inward).

Hello, If you want to do it in a post function, your code would look like this: import com.atlassian.jira.component.ComponentAccessor; import com.atlassian.jira.issue.CustomFieldManager; import com.atlassian.jira.issue.fields.CustomField; import com.atlassian.jira.issue.Issue; CustomFieldManager customFieldManager =…

Hello, if you want to set a link then your code should look like this; def currentUser = ComponentAccessor.getJiraAuthenticationContext().getLoggedInUser() def linkMgr = ComponentAccessor.getIssueLinkManager() linkMgr.createIssueLink(11111, 22222, 33333, 1, currentUser) You can find more details here:…

Hello, It means that the timetracking field is not on the edit screen of this issue. You should add this field to the Edit screen.

Have a look at the Create issue transition. What event do you throw there? Try to log the event name in the listener and have a look what happened. log.error(ComponentAccessor.getEventTypeManager().getEventType(event.getEventTypeId()).getName())

Hello, You can use the Power Scripts add-on to update worklog's comment. Your script would look like this: updateWorklogAdjustEstimate(10000, "2h", currentDate(), "your comment"); You can find more info here: https://confluence.cprime.io/display/SIL/updateWorklogAdjustEstim There is a 30 days trial period for this add-on.

Hello, The Power Scripts add-on can do it easily. You have to create a post function for the Start Progress transition and put there the following scripts: #{Start Date} = currentDate(); You can find more info on post functions here:…

Hello, You can use the Power Scripts add-on to delete such options. Here is the link to the Power Scripts add-on: https://marketplace.atlassian.com/apps/43318/power-scripts-jira-script-automation?hosting=cloud&tab=overview For example, to delete the "Option" from the global context of custom field "Select List" would be…

Hello, If you are on Cloud then you can use the Update Issue Custom Field post functions. If you are on Server, you can do it with the Power Scripts add-on: https://marketplace.atlassian.com/apps/43318/power-scripts-jira-script-automation?hosting=cloud&tab=overview With this add-on you can create a post function with a…

Hello, If you are a Jira administrator, then you should have the Jira Settings button: You can gran the Jira Administrator permission by including a user to a group, which is granted the Jira Adiministrator permission in the Global permissions. You can see Global permissions by going to Jira Settings -> System -> Global…

Hello, The problem is that when you change a field on a transition screen the Generic event fires by default. I guess, that is your case. Add Generic event to your listener.

Hello, I have the same problem. That is because the real user is stored in the Tempo database and when you restore your backup from Cloud to Server, this data are not moved. That is why you have the Tempo Timesheets user. To solve this problem I am writing a program.

Hello, The problem is that ComponentAccessor.getProjectManager().getProjectObjects() does not check user permissions. You should first get all projects to which a user has permissions. For example, in the code of @Mark Markov you get all projects, for which the user has Browse issues permission. Then you can already do…

Hello, You can use the Tempo Timesheets plugin for it. You can define worklog attributes. When a user logs time, the user will have to fill this worklfow attribute. In this atribute you can make a select list with your custom values (Analysys, Monitoring and so on). After it you can analize your worklogs on this attribute.…

We had the same setups and we did not have any problems. I did not meet such case. But it does not mean that your statement is not true. It would be good to know the real reason from your admin. To say that multiple mail handlers cause slow performance is not enough. It must be explained why your admin thinks so.

Unfortunately, there is no silver bullet to solve performance problems. You can follow the general guide: https://confluence.atlassian.com/jirakb/jira-applications-performance-tuning-229179856.html And mail troubleshooting guide: https://confluence.atlassian.com/jirakb/mail-and-mail-handlers-troubleshooting-211649643.html

Hello, You can not create a filter, which would show you this info. Filters can return only issues. You need to create a custom field, which would show you this info. You can use the Power Custom Fields add-on for it. It is a free add-on.…