Comments
-
Is the rest of your stack trace the same as Chris's? Can you post the entire stack trace somewhere? thanks.
-
It was a change in 3.0.7, so it stopping working probably coincided with an upgrade of SR.
-
This was changed in Oct last year to support usage when no users are logged in: https://jamieechlin.atlassian.net/browse/GRV-529Sorry about that. I don't think it's the same issue as the OP's though.
-
Looking for a plugin at least partly written in scala... are you using JIRA service desk?
-
hrm ok... does it not produce the right number of issues or there is some other problem?
-
You could try https://jamieechlin.atlassian.net/wiki/display/GRV/Scripted+JQL+Functions#ScriptedJQLFunctions-inSprint(boardname,sprintname).
-
Multi select to group is not supported... would need a converter to handle getting the collection of group objects.
-
Something is out of whack. I'd try to reindex again, and see if that fixes it. If not, check for silly things like the value in the database being the string "null", or an empty string, although that doesn't explain why you get the hits when you run sql. > 'm trying to grok is where/how something joins on that field and…
-
The script runner has a copy project built-in script which can clone an existing project, including its custom field associations etc. Also IIRC the jira cli can do the same. Not sure.
-
userUtil.getGroupsForUser("ces")*.name Will give you a java.util.List of the group names.
-
You use a post-function to create the sub-task, with the condition above. Is that what you're saying?
-
Can't read those screenshots. What version of jira? How were the subtasks created, presumably through code otherwise you wouldn't have put the script runner label?
-
You get it from my.atlassian.com if you have a licence.
-
You're going to need two sets of filters, one for A-related issues and one for the Bs. Then instead of using the favourite filters gadget you need a version of it that selects filters by regex or ID, eg Filter+List+Plugin - but I'm not sure if that one's kept up to date...
-
And see https://answers.atlassian.com/questions/29830/is-there-some-easy-way-i-can-implement-a-customizable-top-menu-bar-so-i-can-navigate-between-confluence-jira-crowd-etc
-
Start at https://studio.plugins.atlassian.com/wiki/display/GRV/Scripted+Fields ... it's overkill though for what you're trying to do imho.
-
There is a code example here for getting the two parts of a cascading select: https://jamieechlin.atlassian.net/browse/GRV-42?focusedCommentId=45504&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-45504 Personally I'd consider solving this problem with an excel macro rather than redundantly…
-
No, it's implemented as a listener, but not the old style that you could just remove admin -> listeners.
-
If you have script runner, the following lines pasted into the script admin panel will disable autowatching for all users: import com.atlassian.jira.component.ComponentAccessorimport com.atlassian.jira.user.preferences.PreferenceKeysdef userManager = ComponentAccessor.getUserManager()def preferencesManager =…
-
You could easily run a few lines of groovy to change the autowatch preference for users, but the problem is when new users join. I guess you could write a UserEvent listener which turns it off whenever someone signs up.
-
It's a bit of an oversight that they have not made this disable-able, imho. It's not even a plugin module so you can't disable it. If you can't recompile a class, you may have to rethink.
-
Using pgAdmin III for instance, or psql.
-
It would be easy as a groovy script, but probably I'd just use a bit of sql: select project.pname, max(updated) from jiraissue inner join project on jiraissue.project = project.id group by project.pnameorder by 2 desc
-
Probably not change as I guess you already run jira on it, instead create an additional CNAME record.
-
yeah that rings a bell. Try setting the logged in user at the top: ComponentAccessor.jiraAuthenticationContext.setLoggedInUser(...)
-
There is no current logged in user in a service. Even if you run it manually. Can you add some logging so you can see at what point it gets set to a null value.
-
The first line doesn't look correct. I think you want: ComponentAccessor.userManager.getUserByName("admin") see https://scriptrunner.adaptavist.com/latest/jira/recipes/jelly-migration.html#_in_code
-
yep, ".created" will call isCreated() in preference to getCreated(). IIRC this is the only place where I've had this problem.
-
setReporterId takes the user key, not the user name.
-
Hi... I think it will be the case that either all options will be possible, or all options not. If you change the plugin-supplied CF, and some other CF, do you get notifications? Does the changed value for the plugin-cf appear in the history tab? You could try copying the value to a comment on change, but if it's not…