JamieA Expert

Unfortunately not.

Good question... the next release will include the integration test runner that I have been using for development of scripts and stuff for the last 5 years. It includes supporting classes to create temporary test projects and workflows and so on. If you can wait a few days or a week you can try it. Or contact me and I will…

It's been made a bit harder recently, probably the easiest way is to go to: http://jira/browse/PKEY#selectedTab=com.atlassian.jira.plugin.system.project%3Acomponents-panel ie the components tab on Browse projects, then mouse over the components. The ID is the last part of the URL. Or, you could look up in the database, or…

In general it's not a good idea to have code write other code... it gets impossibly difficult to debug and deal with escaping issues. But, I have not tried it, but if you write javascript using the setHelpText() method it will probably work. What is it that you're tried to do, it looks like remove a version option that has…

Seems like a good thing to try... Probably text to number is not supported, but as April said you can create a (Number) script field which gets the text value, and then use the built-in script to copy from the script field to the number field.

I think this is something specific to Jira Misc Workflow Utilities? issue.get(x) points to something other than an Issue object, and I think JMWE uses a wrapper.

You can't use eg componentManager.getCustomFieldManager in JIRA 7. See https://scriptrunner.adaptavist.com/latest/jira/releases/UpgradingToJira7.html#_removal_of_componentmanager_methods When you've fixed those probably everything else will work.

The first issue causes the others. Is this a workflow function? transientVars should work fine. Can you add a screenshot of the function config.

You should link to the issue you created, I would vote it up. I take Nic's point, but if you had a general permission "Move items through the workflow", you could easily lock it down to developers or whatever. If you wanted more specific conditions you could just add Anyone to that permission, then use workflow conditions.…

Exactly as Andrew says. You want Admin -> Script Listeners -> Create a subtask. Under "expand examples" there are, well, examples for checking for field changes.

Try using "latest" instead of "2.0.alpha.1". The api url changed in recent versions of jira. If that doesn't work you could check the rest api docs.

Hi @Adam, > Your example works perfectly Cool, feel free to vote up my answer/comments ;-) > Just out of interest why is setTimeout such a bad thing The problem is, you have a timeout of 2 seconds. Either that's too long, in which case it's just time wasted, and the user can see the link which then disappears causing…

I've updated the answer with a complete, tested, working example for hiding the dashboard options unless the user is in jira-admins. PS - try to avoid setTimeout. > When i ran an alert after the code it was before the dashboard had even started to load so how could it hide something that wasnt displayed The point about…

So get Chrome, go to the dash, press F12, click the console tab, and just paste in AJS.$("#dash-options").hide() If that doesn't work then there's some other issue to deal with.

It wouldn't be in any of those places. If there are javascript errors it will show in the browser.

They're both the same, the second is just a more verbose version of the first. Yes, just look at the page source, and look at the console for any errors.

That worked for me... where did you put the code? Are you sure it got through to the page source? what jira version is it?

upvote then, please!

How about doing it with some javascript... would not stop direct url access but you can remove the links to configure the dashboard. Here is a complete example. The only thing not shown is the <script> tags if you choose to put this in the announcement banner. (function($){ $(function(){ $.get(AJS.params.baseURL +…

But to answer your question, it seems like for checkboxes the validatior is not firing when the form first loads, as it should. To work around this you can use an initialiser to set it hidden at first, or just use the configuration options on the field in the behaviour.

or a single checkbox...

Why don't you use radio buttons? Being able to tick both Yes and No doesn't make any sense.

That metric changes through the versions.. in 4.2.2 you have Content (All Versions), and current versions. I assume it's the number of content objects, ie pages, blog entries, comments etc. It's just the number of rows you have in your "content" table.

Have you actually verified this is the case? Admitted I wasn't able to use full LDAP integration, for various reasons, but the delegated LDAP auth works by looking up the user's full DN then attempting a bind operation with the supplied password. I suspect the other directory types work the same way. The alternative is to…

no worries, thanks for updating this.

We'll work on the support ticket you have created, then when resolved make an update here for others.

I think both cru and bam will create the issue via REST? Although I'm not sure about that, they might use something like the Issue Collector. You could see if webwork.action.ActionContext.getRequest() is empty... if so it's being created via rest (I guess) so allow it. You could also look…

You need to be a bit careful that the assignee is not null, so I would surround it with:if (issue.assigneeUser) { ... }

You could use the following as a listener on the Assigned event: import com.atlassian.jira.component.ComponentAccessordef watcherManager = ComponentAccessor.getWatcherManager()watcherManager.startWatching(issue.assignee, event.issue) untested, and that's for 7.0. In 6.x you may need to convert the user from one type to…

What version of script runner? The version that is compatible with jira 5.2 supports java 6. Somewhere you have got some misalignment between test and prod.