JamieA Expert

Are you using the latest version of the plugin for your jira version?

See http://confluence.atlassian.com/display/JIRA/Plugin+Developer+Notes+for+JIRA+4.4#PluginDeveloperNotesforJIRA44-Single-andMulti-SelectCustomFieldChanges You will need to look up the correct Option for the value 2-High. Not really sure what you mean by inheritance though, this is a plugin you're using? If so maybe…

getFieldById("assignee").setError("blah blah") Don't forget to clearError() when the value is OK.

I would use a behaviour on the assignee to compare with the two other fields, and set it to invalid if it's the same, with a sensible message. Think this will be easier and less confusing than trying to set the available assignees.

There was a problem in one version - which version of the plugin and jira are you using?

You didn't specify the plugin you are using so I'll give you the answer for ScriptRunner for Confluence... it's probably the same for others. Get the current user with: import com.atlassian.confluence.user.AuthenticatedUserThreadLocalAuthenticatedUserThreadLocal.get() // gets the current user Not sure why you need the full…

There is a sample for this here: https://scriptrunner.adaptavist.com/latest/jira/testing/testing-workflow-functions.html#_example_scenario

For example the following would be true if there is a component call Foo selected: "Foo" in issue.getComponents()*.name

if you click Edit you can get the behaviour as xml, which will save you configuring the fields manually. Then you paste that into the target system. I understood you only deleted one behaviour, rather than all of them.

If you've deleted it you need to restore the database to another instance and get it from that.

You don't have to include it in your plugin - in fact doing so is not going to work if there are components etc. As Ash said, you should be able to use @WithPlugin and @PluginModule to get access to the services.

It is possible based on issue type... check the docs: http://confluence.atlassian.com/display/JIRA/Adding+a+Custom+Field#AddingaCustomField-CustomFieldContext

Why do you think they have been solved by Github Enterprise? Last time I looked, GHE was shipped as a single virtual appliance, and couldn't be clustered. It's the reason they are marketing it as the only scalable self-hosted git solution.

Or similar to Vincent's suggest - create a global transition with a post-function that executes one line of script: reporter = assignee (make sure it's first post-function in the list). And then bulk transition all issues through that transition.

Run a query, for each issue update it so that reporter = assignee or whatever. It's going to take you longer than doing it manually if you don't have experience, but it will set you up to do more automation tasks in the future.

We all had to learn once ;-) Anyway, hopefully that sort of problem would come out in testing...

Should be the following, otherwise you will get NPE for issues with no components. issue.getComponentObjects().getAt(0)?.getName() Creating a script field for testing is a good idea, you don't need to assign it to any issues. Or personally I just use issuemanager to get an issue, and test in the admin script panel.

your imports need to be in <% %> tags as well.

It's the same in an email template as in any script, more or less. Use com.atlassian.jira.security.groups.GroupManager#isUserInGroup to check if a user is in a group. Google for the javadoc. For getting a custom field value there are countless previous questions about this. 

Hi - good question. A script macro for this is pretty straightforward. The config might look like: image2016-5-31 14:58:12.png No parameters are necessary. The code is: import com.atlassian.confluence.pages.Pageimport com.atlassian.confluence.xhtml.api.MacroDefinitionimport…

Same problem with Bonfire. I also have complained to Atlassian that this is "on by default"... I think it should be opt-in, not opt-out.

Start with https://bitbucket.org/jaysee00/example-confluence-sso-authenticator/. IIRC that sample code gets the user from a header request. It's a very minor change to get it to read the authenticated user name from the request. We do it exactly the way you describe in your bullets, works fine. We only use mod_jk for the…

I don't think there's a problem with restore - just make sure they're defined in entitymodel.xml and then they'll be backed up and restored just fine. Just try to choose table names sufficiently specific such that atlassian won't add them in the future.

@Virgil Carcu if this is still an issue can you add the versions please.

Just cleaning things up. Problems are scheduling are fixed by upgrading to, I think it was, 3.1.3. All the scheduling code was rewritten and should be much more reliable.

Yes it is...

I wrote some code very recently to do this. You should have little problem translating to java: https://studio.plugins.atlassian.com/wiki/display/GRV/Scripted+Fields#ScriptedFields-TotaltimethisissuehasbeenInProgress The listener has access to the issue, that's all you need to use the code above.

Can you say a bit more about what the script does? How does it distinguish between issues created by email and others?

Not sure if this is your use case, but I think the hole in this "email me my own changes" is when people create issues through email. I think that that should disregard your preference, because you will nearly always want to know the issue key and link for the issue that you created.

Quite a surprising ommission. More info here: https://answers.atlassian.com/questions/1715/how-do-i-combine-the-activity-stream-for-jira-confluence-fisheye-etc , rfe is here: https://jira.atlassian.com/browse/JRA-19667