Alexey Matveev Expert

You could use an add-on for it. Time in Status https://marketplace.atlassian.com/plugins/com.obss.plugin.time-in-status/server/overview If you want to write your own custom field then you would need to go through the issue history and calculate time in status based on the history.

In what applications are you trying to construct and parse a generic JSON? 

The problem is not about poos-max-size. The problem is about your SQL queries which execute too long. If you can not optimize your SQL queries, then you can ignore it. But it could be a peformance problem later.

Right now your Jira instance uses relative dates. If you are on Jira Server/Data Center then you can follow the following KB to switch your Jira to absolute dates: https://confluence.atlassian.com/jirakb/disable-relative-dates-in-jira-applications-414187622.html But you will have absolute date in all Jira. Not only in…

Those buttons are defined by Transaction Names in the issue workflow. If a button is present on the detailed issue view it means that the issue status is defined as outgoing status for the transaction(button). You should check the workflow configuration for the issue. If you do not need a button for a status then you…

You can try to use this Rest Api https://developer.atlassian.com/cloud/jira/platform/rest/#api-api-2-licenseValidator-post

You can find how to create service with ScriptRunner here: https://scriptrunner.adaptavist.com/5.3.1/jira/services.html About the warning you can read more here: https://jira.atlassian.com/browse/JRASERVER-45794 Basically it means that your sql query performs too long and Jira warns you about it. It is not a error, it is a…

Kindly make sure that your user has a Jira Software license. You can go to user management, choose your user and have a look at the Applications column.

I think you are talking about ScriptRunner. If so then the code would look like this issue.setAssignee(issue.getParentObject().getAssignee())

It is ok. I just checked. I also do not have the dependencies in my pom. If you need them, just add the dependencies.

What do you mean by "manage the version by component"? Do you mean that you want to use Jira versions somehow related to a component? I do not think it is possible out of the box. Versions are created for the whole project not for components. You attach issues to versions. If you want to attach issues with a certain…

I am a bit confused now. You said that you made fields required fo sub tasks and then they are not checked on transitions, right? I said that you can not create a sub task if the fields, which are required, are not provided. But you can create such a sub task? Do you mean that you can create a sub task without providing…

If you have Power Scripts or ScriptRunner plugins then you could write your own JQL function.

The new Jira UI is available only for Jira Cloud.

Look at the plugin called NFeed https://marketplace.atlassian.com/plugins/com.valiantys.jira.plugins.SQLFeed/server/overview or Power Custom Fields PRO https://marketplace.atlassian.com/plugins/com.keplerrominfo.jira.plugins.keplercf-pro/server/overview

Kindly have a look at this KB https://confluence.atlassian.com/jirakb/how-to-change-the-default-session-timeout-604209887.html

If you set a field required in the field configuration scheme then Jira will require the field even if it is not on the screen. You can have different field configuration schemes for each issue type. You can make a different field configuration scheme for subtasks and did not set the field as required there. In this case…

I guess you marked a field required in the project field configuration scheme. This setup is valid only for the create and edit screens. If you want to make fields required on a transition you should use an add-on. Kindly read the following KB…

Do you mean that some users can not see the status field?

Could you provide the script for 2 pick lists? The script would be basically the same for 3 pick lists. I could modify it.

Yes, everyone will see it in the issue detailed view screen.

1. You remove the field from the edit screen. 2. You create a screen with the field 3. You create a transition with the screen 4. You set permission condition for the transition Only users with the permissions, which you provide for the transition, will be able to execute the transition and change the field on the screen.

You do not need an issue key. You need to know the project. You can query the project by jiraHelper.project You can see it in the example in the ScriptRunner documentation.

You can use the Big Picture plugin. There are baselines like in MS Project. https://marketplace.atlassian.com/plugins/eu.softwareplant.bigpicture/cloud/overview

You should create a web panel in ScriptRunner. Kindly have a look here: https://scriptrunner.adaptavist.com/5.3.1/jira/fragments/WebPanel.html

There is no reduction in the Original Estimate field. It does not change, if you log time. The Remaining Estimate field changes. There are 2 fields: Original Estimate, Remaining Estimate. Original Estimate never changes. Remaining Estimate changes according to logged work

You can find the following text in Scriptrunner documentation Unfortunately, at the moment, your function must reside under the com.onresolve.jira.groovy.jql package for it to be found. (You can create these directories under one of your script roots). Which means, that you have to create…

You can not add or remove columns from the linked issues view. But you can use an add-on, which will let you define your own columns for linked issues. For example, Issue Matrix https://marketplace.atlassian.com/plugins/com.botronsoft.jira.issuematrix/server/overview

If you use LDAP then you should setup Kerberos. In this case you will be able to use SSO

There must be the Restore System option under External System Import. I guess you are on Cloud.