JamieA Expert

There was a bug introduced recently which caused this, but was fixed in the release yesterday: https://productsupport.adaptavist.com/browse/SRJIRA-2129 Please could you upgrade to the latest version: https://scriptrunner.adaptavist.com/4.3.16/jira/releases/current-release.html

It depends what you want... you can make your code fire only on Create by doing: if (getActionName() == "Create Issue") {...} but check that is the correct action name for your workflow. That's probably the best approach. Your code is not working because getValue will return null rather than an empty string, you could…

There is nothing in the API to support that AFAIK. You could do a lucene query on the worklog index (6.4+) but I don't think it's worth the trouble, and may not use any less resources. You could use com.atlassian.jira.issue.worklog.WorklogManager#getByIssue(com.atlassian.jira.issue.Issue, int), so get a paged list. If you…

can you find more of a pattern? So when you refresh it works. When you navigate away and come back does it still work? For how long does it work until it stops? Does it fail like this for all users?

Actually that seems unlikely to be the cause. Can you check the logs for any errors?

I can't reproduce this. Is it possible the user is not authenticated the first time they hit the dashboard? Do you have SSO and is your jira also available to anonymous users?

I'll double check when I can, but I know this works for me... what jira version?

Strange... this definitely works for me. Did you select the "number" template or some other?

As I asked you on the other place, do you see the value in the issue navigator when you add the column to the output?

OK, just remove the conn.close line. I would reindex and look for errors in the logs.

I agree with Dieter, if it's possible to do it in JQL then I would use that. Is it? If so we could give an example for using JQL. If not, I would write it like this: https://gist.github.com/2438750 (not tested). I'm not sure about closing the connection, the javadoc implies that closing the Sql object should close the…

It did work at the time, but this was back in the 3.13 days.

Thanks for posting. Personally I feel that you should let bigger users opt-out until they feel that the add-ons are worth the money, rather than just left smaller users opt-in. The two performance issues James mentioned are really not big-ticket items, and also everyone gets the benefit, not just the customers paying the…

Thanks Nic. Atl Uni - we will try to make use of it if we are going to pay for it, sure, but it wouldn't be in my top 5 enterprisey requests... sounds like it probably wasn't your key request either.

I would also like to know which enterprise customers they spoke to, as Scott Farquhar mentioned in his blog entry ("We created a new position “Director of Enterprise”, and interviewed hundreds of partners, customers and our customer-facing staff."). They asked us for some metrics, and we are row 6 in that screenshot. They…

Andrew, yep, I saw that in your comment below. And no doubt my client will take advantage of that. But 2 years can pass quickly (you know what I mean), and we've been waiting many years for the features mentioned above. So I've no faith that they will be delivered within 2 yrs, and I see nothing indicating that they are…

"then they'd seriously consider it" - but what's the alternative, not upgrading anymore? On first reading of the new pricing I'd assumed that my client would stay on vanilla non-enterprise pricing, as they don't want the extras. However looking at it it seems that that's not an option if you have more than 500 users?

Hit the nail on the head. My clients would probably be quite happy to pay the extra for any of those enterprise items, or even a step in that direction. Or in the absence of those, per user not per user per instance pricing. "Enterprise" is not even the right word for this new offering.

Correction - Balsamiq have taken the sensible option and offer an ELA regardless of the number of instances. I wish Atlassian would go a similar direction.

Yeah, it's a massive increase. Agree about the "enterprise" options, almost worthless. I can barely remember when the last time Atlassian support actually solved one of my company's support calls. I wouldn't mind, if they were charging per user, but actually they're charging per user per instance, and absolutely refuse to…

Isn't the Rank(Obsolete) field, err obsolete? Don't you also have a Rank field?

Have you created an applink for the crucible project, in addition to the fisheye repo?

duh, i got it wrong - please try: https://gist.github.com/jechlin/f951aff26dd83197cba1e88b66683a6d

hrm it wasn't when I ran it, they were indented... maybe I screwed something up somehow. You can just change the "depth++" to a 0 to turn off indenting.

You can use something like this to print the option values with nesting. Should also work with multi-level cascading select. import com.atlassian.jira.component.ComponentAccessorimport com.atlassian.jira.issue.customfields.manager.OptionsManagerimport com.atlassian.jira.issue.customfields.option.Optiondef optionsManager =…

Nice... alternatively you could use some monitoring tool that can use JMX to get this info and chart it etc. Maybe JavaMelody has it - although I don't think so.

We've done this to death... check https://answers.atlassian.com/questions/145062/permgen-problems-with-scriptrunner. You may be using another version of groovy. If not just bump the permgen and XX:ReservedCodeCacheSize as per the question above.

From the background I suspect it will be a marketing push for blueprints.

Can you add some logging messages in there so you can see the intermediate values in the app log. Also please use the {code} macro, it's unreadable otherwise.

Have you tried? "Locked" just means that JIRA or the SD plugin manages the configuration of it, ie the associations between projects and issues, screens and whatnot. I don't know the type that field expects, so can't really give you any sample code. It might be difficult, but it will certainly be possible one way or…