Comments
-
Amen to that... a list of thousands, with 50 "Apr 2012 Sprint"s is useless. I don't see why the function could not take into account the clauses already entered... not trivial but not beyond the wit of Atlassian's superstar programmers.
-
In my humble opinion - don't consider Fisheye. It doesn't scale well. So far my experiences with Stash have been very positive, although feature-for-feature it does not compare with Github FI. The Stash team are making rapid progress though. For code reviews you can use gerrit so far as I understand. You could also use…
-
I suspect not, but try it.
-
Me too, I had to do it with Fisheye and it worked fine. Therefore my advice is: give it a try, it will probably work!
-
Yes, you can filter out values depending on attributes of the user with the behaviours plugin. Other options might be database values plugin or nfeed or something, where probably you can modify the sql query according to the current user.
-
Also have a look at jirasu plugin.
-
The script runner plugin has a facility for becoming someone else... admin -> built-in scripts -> impersonate another user.
-
I don't see how you could do this with JQL. I would write a script that fetches the set of reporters, then remove anyone that has the ASSIGNABLE permission... that should give you the list of customers.
-
It's kind of tough to work this out retrospectively. Have you got some thread dumps from during the period of very high cpu load?
-
It all depends on your code. There's nothing specific I have to warn you about though, if you are using simple stuff and the @PublicApi you should be fine. You should test your major areas of functionality by upgrading a copy of production first.
-
If you want a JSS answer create a new question and use that plugin's tag.
-
that's an error from jira scripting suite... double-check what plugin you want to use. Use JSS for python, ScriptRunner for groovy.
-
"status changed to Open" - doesn't that work?
-
that is, use addLabel, rather than set all labels. Also, it's a bit confusing that in your example you're adding a called called: labelToBeRemoved!
-
Couldn't this just be: import com.atlassian.jira.component.ComponentAccessor def user = ComponentAccessor.jiraAuthenticationContext?.getLoggedInUser() def labelManager = ComponentAccessor.getComponent(LabelManager)labelManager.addLabel(user,issue.id, "my-new-label", false)
-
Possibly you have a bad code in one of your script fields, this would break the index as is discussed in the docn.
-
No, it's a problem that occasionally happens on startup, fixed in the next major release.
-
Check that the plugin is enabled in the plugins section, also check the logs for errors. You should see a "subversion commits" tab even without any repos configured. Also check the project you are looking at is actually using the default permission scheme.
-
You're correct, you don't need fisheye. You will see the "view version control" permission if you are looking at a permission scheme, but from what you're saying it sounds like you might not actually be a jira admin... maybe just a project admin. By default I believe the Developers role has that permission.
-
Out of interest I pasted your code in SR in 4.1 and it shows me: image2015-9-17 12:42:14.png The issue is that you're using issue.getSubtasks(), which is deprecated and returns a list of GenericValues. You should use issue.getSubtaskObjects(). My other suggestion would be to use a custom template that truncates the value…
-
Are you using Send custom email built-in script? If so you just need: issue.statusObject.name
-
Fair enough. I would check if possible that one instance can handle it. I cannot make one instance of fisheye/crucible cope with the amount of repos and projects we have. 2.9 seems to have a memory or resource leak where it needs restarting every two days.
-
Could you not just copy the entire database, then delete everything you didn't want from it using the web UI. At least this will take you down a "supported" path... I don't believe there is anything in the published API that will allow you to successfully migrate a crucible project with all reviews...
-
Do you want something more than: status WAS "Closed" and status WAS "Reopened" and status not in ("Closed", "Reopened")
-
Still investigating this in another instance, will get back to you.
-
OK. Can you check the logs for errors? Most likely something is failing. If so could you create a bug at https://studio.plugins.atlassian.com/browse/GRV.
-
Doesn't work in what sense? I mean if you disable and enable the entire plugin from manage plugins, that should get everything working? I'm still working on reproducing the causes of the log message.
-
BTW disabled and enabling the script runner plugin should remove the error and get things working, but only until the next time this unexpected thing happens that I can't work out atm...
-
Hi Aggelos... I'm going to try to reproduce this... unfortunately this is only a problem I've seen in production systems. What version do you have?
-
Kostas, this is an issue that I am working on. I don't think it means there is any problem but yes it it's annoying. You could set the log level to fatal for that class if you wanted, but I will try to get a fix for this soon.