JamieA Expert

There's not a great solution for this problem. I'm not sure why allowInlineEdit = true is not working. The problem is that the current form contents are not available in an initialiser, the rationale being that you can get these values from the issue in the database. The problem comes when you switch project or issue type,…

You can't do this as an initialiser, because currently the form contents are not available in initialisers. Therefore you need to attach it to a field as in Jonny's example. There you can check whether the value is currently empty. You can also use getUnderlyingIssue(), which will return null if this is the Create action…

Try the issue-alternative-assignee plugin: https://studio.plugins.atlassian.com/wiki/display/JUP/User+Picker+From+Project+Role+-+Issue+Alternative+Assignee If you have a relatively recent version of jira, you should use this version:…

What is the library, is it one that is also included in jira itself?

The scope for the servlet API should be provided, not the default, which is compile.

Just a punt, but have you tried clicking the little icon thing at top right? Looks like two rectangles, one grey, one white.

If you want to store transition information use IssueService to make the issue undergo a transition.

Did the email have a different format from the others? If so it was a custom template, and you should be able to find it. If not, is the event definitely getting fired? What's the workflow function that fires the event... is it just the standard "fire an event that can be processed by the listeners"? Check the logs for…

I was talking about a scripted field from the script runner plugin, I'm not qualified to speak to the one you used I'm afraid.

As Christian says. You could add a scripted field which calculated the number of components, which you don't need to put on any screens. Not ideal for ad hoc reporting though. The other thing to do would be to hit the db directly... far from ideal.

It's fine, I don't see any reason not to do that.

Agree. Windows installers seems like a necessity for windows people, but I never had any issue with the original linux distro, just unpack and run. In fact I object to them writing linux installers because it's development resource that they could be using elsewhere. We repack the apps into rpms, source controlling our…

You cannot use those events in a notification scheme, they are not "per project" for one reason. You can run your own code when any of those things happen - see https://scriptrunner.adaptavist.com/latest/jira/listeners.html#_custom_listeners

Uncheck the "copy classic greenhopper config" - you probably don't want it, it's out of date now and will be removed.

That particular example is covered here: https://scriptrunner.adaptavist.com/latest/jira/recipes/behaviours/select-list-other.html

If you want to show them when a component is chosen, you have to add the script to the component field, not initialiser.

JUP plugin is compatible with 6.3... make sure you are using the right version. Setting the value should take a User object. What type is your SIL script trying to set?

You can't do that, and I don't think it should be necessary to. Each committer should only use the keys from their project, and if they're fixing a bug in another project, then fair play...

Normally caused by a plugin with a broken ProjectTabPanel, eg one that is not yet compatible with the version of jira you are using. The jira-svn plugin causes this. If you need this plugin just disable the project tab panel module.

Yes.

The last argument determines whether to raise an event for the new comment or not.

I think you need a plugin, eg JQLTricks: https://studio.plugins.atlassian.com/wiki/display/JQLT/Subtask+Functions You could use the hasSubtasks() with the inverse operator.

Hrm... if you look at some of the 5206 issues, are there any that categorically should not be present? I'm not sure if the backlog in the board is limited in some way. The navigator will show subtasks whereas the board does not, but that probably doesn't explain the discrepancy.

If you use script runner it will add some icons to the planning board, the highlighted ones will take you directly to the issue navigator with the query that represents the backlog or sprint issues, or those issues added after the start of the sprint:

There are some issues on this already... https://jamieechlin.atlassian.net/issues/?jql=text%20~%20%22fast%20track%22%20and%20resolution%20is%20empty can you have a look and see if any match. If it's intermittent it would help if you could try to isolate what the circumstances are that makes it not work properly.

You can't do it natively, but you could do with either or both of javascript and a validator... to make it work properly you might need to disable the issue link operation, so users can only create a link on edit or transition. If you don't do that it's not possible to validate the link.

For what it's worth, IMHO you're completely correct. It's an arbitrary restriction. You may want different workflows and fields for the subtasks, but often you do not, and have to set up various sub-tasks the same as parent issue types is a royal pain. In the same spirit, you should also be allowed any level of subtask…

Or you can just use \{

Jelly isn't a programming language... if you choose ScriptRunner there is some information on typical tasks that people we re using jelly for here: https://scriptrunner.adaptavist.com/latest/jira/recipes/jelly-migration.html

https://answers.atlassian.com/questions/33517/hide-tabs-like-issue-types-etc-from-project-role-administrators#33523 - closing as duplicate