JamieA Expert

All fields are by default copied from the parent issue (where the issue type association is valid). To set custom fields to custom values you need to do more or less as Kostas says. There's no restriction to text fields.

Have you looked at page restrictions? http://confluence.atlassian.com/display/DOC/Page+Restrictions You need to make a group that contains everyone but the restricted members...

You must not have disabled auto-assign in greenhopper - you've definitely disabled this: http://confluence.atlassian.com/display/GH/Managing+your+User+Preferences ?

Go to workflows, copy the jira workflow, go to Start Progress, look at Conditions. I don't think you can create a draft of the default workflow, so you then need to modify the default workflow scheme, adding the edited workflow. Worthwhile testing in a play instance.

Disable auto-assign in the greenhopper config. Then modify your workflow so that the start and stop progress doesn't have the "assigned to current user" condition.

So something like: fixVersions in releasedVersions() and not fixVersions in unreleasedVersions() should work.

Not currently, no... sorry.

This: def summaryField = getFieldById("Summary") should be: def summaryField = getFieldById("summary") For the log line immediately after that line, does it not show the summaryField variable as being null?

Try https://jamieechlin.atlassian.net/wiki/display/GRV/Built-In+Scripts#Built-InScripts-BulkFixResolutions This will allow you to do it without having to stop jira, or reindex.

It's not possible without plugins. For example Script Runner has the expression function, which allows you to do: issuefunction in expression("project = FOO", "assignee != reporter") The first expression is a filter query which you could leave as en empty string to run "assignee != reporter" on every issue.

Write your own calculated custom field type plugin...

Hi... I'm not sure what you mean. If using html use <p> markers.. If you paste more of the template that would help us answer.

You may find it easier to use the cfValues map which is passed in: https://scriptrunner.adaptavist.com/latest/jira/recipes/workflow/validators/simple-scripted-validators.html#_validating_a_multi_select_option_is_selected As Thanos said, with checkboxes it can be multiple. To check for a single specific checkbox being…

I wrote a "mygroups" plugin, which allowed groups to have a set of owners, and those owners could upgrade the groups. I wrote it ages ago, and the source is not accessible to me anymore... I'm just mentioning it to point out that writing such a plugin is quite possible.

I don't even agree with Norman's definition. Won't fix means "Will not", not "Would not", and to me it means that it is indeed a bug but the impact or benefit is not worth the effort to fix, whereas Rejected means the bug could not be reproduced or was a user misunderstanding. IMHO you should keep the list of resolutions…

Hi Keith, The way you think it should work, is the way that it should work. That is, you should not need to apply it to both. Maybe there is a bug with cascading selects triggering their listener when the page firsts loads... but I thought this worked. If you are using jira 6, and the latest behaviours plugin, please feel…

@Matt Moody: ! ('Future Release' in issue.fixVersions*.name) because issue.fixVersions is a Collection. @venkat - same solution.

This is relatively straightforward in Script Runner 3, if you wanted to give that a try, eg: import com.atlassian.greenhopper.service.sprint.SprintManagerimport com.onresolve.scriptrunner.runner.customisers.JiraAgileBeanimport…

Not that I would mind answering general questions, it's just originally you used the ScriptRunner labels. And JMWE has a different api (issue.get) that I'm not familar with.

two in two minutes. that's not ScriptRunner, it's JIRA misc workflow extensions IIRC.

Can you attach a screenshot of the configuration, because I've lost track of what you're trying to do...

Or issue.priority?.name in ['High','Emergency'] which reads a bit more like spoken language, to me.

What that sql does is rename a user... there is a lot of info here: https://jira.atlassian.com/browse/JRA-1549 which is more definitive than the old forums. If your question is specifically about AD then I'd say no, that is not a good resource, but I'm not really sure what you're trying to do. Is it rename a user or…

Can you give a bit of context, eg what is "Tyler's script"?

Still no questions for the bounty hunters, and I think the reason why is it's a bit unclear how to add a bounty. What's the reason it's not available when adding a question...?

Not sure if you were responding to me or Justin, but I just realised I meant to type "rep divided by open questions", not bounty... argh.

Right but the people who have more karma generally have harder questions, so are more likely to need to use a bounty. I think there should be a limit on the number of open questions, say you can't have more than bounty/10 questions open. That will at least encourage people to accept answers. IMHO getting people to accept…

The whole thing is a ripoff of SO, but an open source ripoff.

You can use the "simple scripted validator" where the condition should just be: issue.fixVersions Let groovy worry about whether it's null or an empty collection or whatever.

There has been some questions on here recently about negative interactions when changing an issue in a listener and the AutoWatch listener... sounds related. Personally I could not reproduce the fix with disabling the autowatch listener.