JamieA Expert

Seems to be an old question, but, there is a built-in script for this now:https://jamieechlin.atlassian.net/wiki/display/GRV/Built-In+Scripts#Built-InScripts-SetIssueSecurity You just need to set the condition to check for the issue type you care about: issue.issueTypeObject.name == "Bug"

You should use @Grab... there is much more to it than what you are doing. The classpath needs to be modified at the compile phase, the way you're doing it it's too late. http://docs.groovy-lang.org/latest/html/documentation/grape.html

well, it's there then...

This is included in 3.0.x... presumably you are using an earlier version?

http://confluence.atlassian.com/display/JIRA/Linking+to+local+file+under+Firefox It should be 5 slashes for unc path.

You need to modify the workflows too such that there is a condition that only the Developers role can do the action, then you remove everyone from the developers role. That will let you use the same workflow for the obsolete as for other projects, or you could just put some impossible to fulfil condition in there.…

Is there any error? Make sure you have modified a few issues to ensure their value is in the index. To make new fields work properly you have to reindex every issue associated with the field.

It is possible as above, however you should take the patch that allows you to use the repo name as a parameter to avoid hard-coding it as in Norman's example, think it's this one: https://studio.plugins.atlassian.com/browse/SVN-35 Not a big deal if you have one or two repos but if you have thousands like some svn users…

changeHistoryManager.getChangeItemsForField(issue, "status").reverse().find{it.toString == "Closed"}?.getCreated()

You just need to whip through the changelog and get the date for the last transition where it entered the Closed state. There are quite a few examples about that are very close to that.

dupe of https://answers.atlassian.com/questions/37541156

Zero risk. And that's exactly what you should do unless you want to move the database as well. The instructions they're giving probably cater for moving between DBMS vendors etc.

sorry, I ignored the bit where you said you *weren't* using JSD.

You should put it under <jira.home>/scripts, in your megalis directory, not in the installation directory. I was under the impression that SD comments didn't use the role level, although I haven't had time to check that out, and it seems a bit unlikely anyway.

Thanos's answer should normally be sufficient, except if you have apostrophes or something in the URL. The request returns the created page ID and link, you can get it using something like: new groovy.json.JsonSlurper().parseText(response.responseBodyAsString)["_links"]["webui"] That gives you the part of the link after…

Non-standard custom fields are not supported, as there's no standard way of retrieving the value from them and parsing it. 

thanks. What type of field is ENT_NOTIF_ESCALADO ? Is it called like, all upper case?

can you attach a screenshot of the config and include the versions.

Perhaps it's an empty list. Just use: cfValues['ENT_NOTIF_ESCALADO'] and let "groovy truth" do the work.

You will need ActionContext to get the web request. It's fragile though. See eg https://answers.atlassian.com/questions/139592/check-for-duplicates-link-in-groovy-transition-validation-script

no it should not. Please provide version info.

Are these the right tags?

Inline editing is disabled for this fields where a behaviour is applied (for projects / issue types the behaviour is mapped to). 

Longshot, but did you try add Watchers to the issue security level? Another option might be a user custom field, which is copied to the watchers in a listener/post-function.

I'm possibly missing something here, but can you not just give the Reporter the "Manage Watchers" permission in the permission scheme?

Brilliant, thanks for answering this Ahmad.

It does not at the moment, I have created https://productsupport.adaptavist.com/browse/SRJIRA-1909, although there are other ones that are similar. Please vote/watch it, so you get a notification when it's done.

for 4.3 you need to do it the old way AFAIK.

I wouldn't modify any of the files in jira. Instead, add the following using a web resource context, or just put in announcement banner: AJS.$(function () { AJS.$("#project-config-versions-add").submit(function() { window.location.href = "http://www.google.com"; });}); That's just an example - you should check the return…

It's done through a rest call in 4.4, so I think you would need to write some javascript to plug in to that. It won't be as simple as the old way.