JamieA Expert

Yes, it's a "special" greenhopper link. Link types have a style, eg subtask links, greenhopper links, and then the other types that you see on the Issue Linking admin screen. Only the links with no style attribute are shown in the issue links section. You could make it show them, but you'd have to do a small amount of jira…

This is not documented anywhere. Atlassian really need to answer this seeing as there is no source for Fisheye. And where is the "poke Atlassian" button? Update: I think it's kind of bullshit that this is not documented. The solution above looks feasible but don't work, at least on 2.5.6. My workaround for this: Open the…

It's immediate in the hosted version, should be the same in the ondemand version.

I was going to comment pretty much the same. Does it not work?

Did you try using WorklogManager to create the worklog? What have you tried so far?

Please could you create an issue at https://productsupport.adaptavist.com/servicedesk/customer/portal/2 - then we'll make sure we trace this through to completion, as Answers only has a couple of days left.

If it doesn't work in 7.3 it's a bug, which means possibly we're missing a functional test. I'll ask someone to take a look and get back to you. We may need you to create an issue at https://productsupport.adaptavist.com/servicedesk/customer/portal/2 so we can trace it through the system properly. We'll get back to you.

Hello Roy. Accessing an issue will check the conditions, in your case your workflow must use Simple Scripted Condition. So try the solution...

So when SD is disabled, no problem, as soon as you re-enable, problem?

That's a bit weird... try disabling and enabling the plugin?

Another way is, as Jo-Anne says create a new event and add to the notification scheme. Then with the script runner plugin you can fire that event when the priority is Critical, or changed to Critical or whatever.

I agree with Fahd that this is a bug, but not necessarily that you should create a ticket before establishing it is a bug. In this case though I think it is, although imho com.atlassian.jira.issue.customfields.manager.OptionsManager#createOption should respect the order of creating and not insert them randomly. I think…

It is that one.

No, there is nothing specific here... Not sure what this means: "but I don't see anything in the validator code" Probably best to post a new question with a concrete example of what doesn't work.

As Henning said, test it in pieces, and add some asserts. See https://jamieechlin.atlassian.net/wiki/display/GRV/Built-In+Scripts#Built-InScripts-PowerAssertions

Thanks Henning, fixed it.

The condition should be something like: cfValues['Type'].value != 'Project' || (cfValues['RP Code'] && cfValues['Project']) ie, either the type is not project, or both other fields must have values. Test in Admin -> Built-in Scripts -> Condition Tester.

I would just advise you to put the correct plugin's tag on the question, because the developers don't trawl through every single question on the offchance it's about their plugin.

This is not Script Runner, so I'll remove that plugin tag. 

I don't think you can do it with CSS only but you can use some js, eg: AJS.$("div.activity-comment span.icon-locked").parent().parent().attr('style', 'color:red') This turns all the text red... simple matter to turn the background a pale puce though.

Why can't you just look for: <span class="subText">Restricted to <span class="redText">Developers</span></span> (or whatever)? If it's too hard to do with just css selectors maybe you can use jquery..? Same with the issue security level.

Will get back to you.

The particular script was untested but the behaviour in your screenshot is just wrong. What version of jira is it?

I have heard of a similar problem recently - what browser is it?

That's the date it was closed... the server date is authoritative. You can adjust it for display to clients, but you haven't given any context so don't know what the circumstance is.

There's no method getUsers on com.atlassian.crowd.embedded.api.Group Use for eg: com.atlassian.jira.user.util.UserUtil#getAllUsersInGroups

This functionality is in https://marketplace.atlassian.com/plugins/com.onresolve.confluence.scripting.script-runner. But you would need to change the base url to the old domain, then run the script, then change back to the new base url. It doesn't have the option for you to specify an arbitrary url. Recommend testing on a…

IIRC it will only work for members of the default directory. About 2 days after I wrote it the embedded-crowd stuff was released and I never really caught up.

It's not tested and unsupported when you have two user accounts with the same name in different directories. That's why you are getting the assertion failure. You should upgrade to jira 6 and use the native rename user functionality.

Whilst the US govt and GCHQ most certainly know whether "we" use jira, I don't think we can know whether they use jira. That said I'm sure I've seen some questions from some DoD types. You should probably mail sales@atlassian.com, they will be be motivated to help you answer your question, whereas this community doesn't…