Alexey Matveev Expert

For the first question it is not possible. You need to give users the manage sprint permissions. For the second question you can make a board with a query like this assignee = currentUser()

You should create diffrent screens for the Task issue type and for all other issue types. For the Task issue types there will be the original estimate field and for all other issue types there will be the Story points field. You can find more info on how to create screens here:…

You will get issues, which are update 6 months ago for the "statusCategory != Done" condition. If you want to limit such issue you should write: project = QA AND ( ( statusCategory != Done AND updated > "-2w" ) OR ( status in (Cancelled, Closed, Done) AND updated > "-2w" ) ) ORDER BY updated ASC, Rank ASC

There is an internal variable called issue. That is why you can just write issue.getKey() it will return the key of the created issue.

Could you try like this: #if (! $issue.getCustomFieldValue("customfield_11600")) 

Try to add to the rest call ?fields=*all

Your question was why the edit screen pops up, when you begin to edit a field on the view screen, right? Here is what is in the documentation On the View Issue screen, trying to edit a field with a behaviour will launch the edit issue screen, instead of the normal inline editor. It did not work like that in older versions,…

Try like this #if ($issue.getCustomFieldValue("customfield_11600") != null) 

You could use a free add-on Power Custom Fields https://marketplace.atlassian.com/plugins/com.keplerrominfo.jira.plugins.keplercf/server/overview You can create a custom field, which would show you such info and put the field on the dashboard. You can do the same with ScriptRunner, nFeed.

You can use different estimation for Story and Task (add proper fields on the create, edit and view screens). But for a board you can choose either story or original estimate.

You can do it with Power Scripts or ScriptRunner addons. In Power Scripts you can use Live Fields. You can find more info here: https://confluence.cprime.io/display/TR/Show+custom+message+field+based+on+select+list+value In ScriptRunner you can use behaviour. You can find more info here:…

I do not have safari. I think you d better ask Adaptivist.

That is how scriprunner works. You can find it in sriptrunner documentation. I ll try to ask somebody from Adaptivist and let you know. Or you can open a ticket in Adaptivist support .

Hmmm. that is strange why the code makes your edit screen freeze. Kindly have a look in the logs and try look for errors. 

You can use in your plugin anything, what is available for java to connect to db. For example jdbc

Go to the required workflow, choose add post function, then choose Script PostFunction, then Custom Script Function and write something like this import com.atlassian.jira.component.ComponentAccessor import com.atlassian.jira.event.type.EventDispatchOption def user =…

There is also a problem with import in inline scripts. I solved it like this: import com.atlassian.jira.component.ComponentAccessor def parent = getClass().getClassLoader() def loader = new GroovyClassLoader(parent) def utilHelper = loader.parseClass(new File('groovy/util/UtilHelper.groovy').text);…

If you have such plugins as Power Script or ScriptRunner, you could develop such post function.

Unfortunately, I can not write a script for you. I do no work with Scriptrunner for Cloud.

I tried the code above in the create screen.

Kindly have a look at the Issue Templates for Jira plugin: https://marketplace.atlassian.com/plugins/com.intenso.jira.issue-templates/cloud/overview You can write your own plugin, or use ScriptRunner or PowerScripts. But you would need to write code in this case.

If you want to trigger a transition on update, then you would need to write your own plugin or use such plugins as Power Scripts, ScriptRunner, Automation For Jira. If you have any of this addons, kindly let me know.

I just tried your code and it worked for me. You can change the code like this def apply = getFieldById("customfield_19896") log.error("apply: " + apply) if (! apply.getValue()) { apply.setFormValue("Hi do not replace the revision value kindly update here") } Then open the necessary screen and have a look in the logs. In…

I am not sure how your screenshot relates to your question. 

Go to Applications -> Application Access. the group "administrators" must be one of the groups, which memebers become Service Desk Agents. Remove the group and Service Desk Agent role will be revoked from all users in the administrator group.

It is a static error. Try to run it and have a look at the result.

I am not sure I understood your question. There are issue types and request types. You can associate several request types to one issue type. But you can not associate multiple issue types to one request type.

You would need a plugin for it like JEMH or JETI https://marketplace.atlassian.com/plugins/com.javahollic.jira.jemh-ui/cloud/overview https://marketplace.atlassian.com/plugins/com.metainf.jira.plugin.emailissue/cloud/overview

That is right. You will have to wait until the new priority will be changed. But it does not mean that users will not be able to use Jira. Users will be able to use Jira.

If you delete a priority, Jira will ask you to what priority you want to move issues, which are set to this priority. You will have to choose the required priority yourself.