Amir Katz (Outseer) Expert

Scanning the above answers, two points to consider: * Issue Matrix is a paid add-on. I think it's great, but we're not using it (yet). * Some differences between epics and sub-tasks:* To use sub-task, it must be added the project's issue type scheme, a workflow must be defined, etc. * A sub-task's parent must be in the…

I ran into the same problem. If you don't mind using an add-on (paid one), here is a solution. We are using JMWE add-on and it includes this validator: Field Required Validator (JMWE app) It works correctly, when looking at the field 'Time spent'. BTW, the built-in Jira validator (the problematic one) displays this logged…

JMWE = Jira Misc. Workflow Extensions. Very useful add-on.

It seems that the workaround suggested in the Jira Cloud ticket does not always work in server and I still get results with empty values. What I have devised is not a general-purpose solution, but it's what I needed, and it may be useful for others. Use Case Export some custom fields values in order to import them into…

Would appreciate if you mark my answer as Accepted. Hate to do it myself...

The same bug exists in Jira server. I'm 100% sure that a similar workaround was suggested for it... Can anyone locate that thread?

I totally agree this is a major degradation. The Jira Cloud product managers are totally disconnected from their users (and I'm being polite here). Anyway, here is an ad-hoc workaround (which requires neither any add-ons, nor creating any dashboards): * Run your search * Export --> Print list * A new browser tab will open…

Thanks for the excellent explanation of this mystery. And I totally agree with "poor design choice". It's not the only place...

Yes, I can see it documented in both places, but there is no explanation why one would have to use the New construct. I see that New is used for user , issue, and a few more types. The usual JMWE validators use constructs like 'issue.comments', or 'issue.customfield_12345'. So can please you explain when one needs to use…

Great answer by @David Fischer , but I have one question: Wat's the purpose of the 'new' keyword? I have not seen the 'new' mentioned in the documentation, which, not incidentally I guess, was written by the same David...: https://innovalog.atlassian.net/wiki/spaces/JMWEC/pages/935362565/Build-your-own+scripted+Validator

Thanks a lot! We do have both ScriptRunner and JMWE, but the automation is no-code, which is certainly tempting. The 3rd option - this is a migration from server to cloud, so I don't want to burden my users with additional fields. Update: Just implemented it with automation - easy-peasy! Will not check JWME option at this…

But I'm looking for a better solution which will not require editing...

Here's a kludgy method that works. Let's say the field is called Brand-Model and has these options: * Ford* Explorer * F150 * Chevrolet* Camaro * Corvette * Tesla * Jeep* Defender * Cherokee You do this: * Admin -> Custom Fields -> Brand-Model -> Configure -> Edit Options * Select all the options with the mouse * Copy &…

If the task at hand is to duplicate a custom field (with select or cascade), to a new field in the same server, then you can use the ScriptRunner built-in script 'Copy Custom Field Values'.

I have not touched this since posting my response (to my own question). It was just an annoyance, not really a bug. In any case, please be aware that Jira is migrating to the cloud, and Behaviours will not be supported there, so don't pin your hopes on them. Amir

Comment for method #1 - it works better if you can edit the page. When viewing the page, you cannot select the header line since all column headers are clickable links used to sort by that column. If you edit the page, you can select all rows.

Just FYI: The link (iamdav.in/2014/...) is dead.

I wholeheartedly support what @Chris Annal said above. I am also not receiving any commission from Adaptavist :-). To me, ScriptRunner has proven itself in at least two categories: 1. Provide solutions to problems that Atlassian should have but never did. An example is the built-in script to bulk-import custom field values…

I agree that a new numeric field is the best solution. There are two ways to go forward: 1. Create the new field, run some automation/scripting on all existing issues to bulk-copy the old field to the new one, then modify the new-issue/edit-issue screens to hide the old field and show only the new one. Basically, you're…

Quick update: we're running Jira 8.8.1 (on-prem) and the REST API call still does not retrieve remote links.

Hey Rahul, This is not a new answer, so can you please create a response under the relevant answer above and then delete this one? It will avoid confusion for people who follow the question. Thanks, Amir

See my two suggestions above (Jun. 20, 2019)

So the next step is to open a support ticket with Adaptavist. You're paying big $$ for ScriptRunner, so you're entitled...

There are two ways to get the project key in a Behaviour script: def projectObj = underlyingIssue?.getProjectObject() if (projectObj) { projectKey = projectObj.key // Plan A } else { projectObj = getIssueContext().getProjectObject() projectKey = projectObj?.getKey() //plan B }

You mention Behaviour. I assume you mean the feature that comes with ScriptRunner. If that's the case, you cannot do that - the Behaviour groovy code is translated into Javascript code that is injected into the web page. Cloning runs in the background and does not display any user-editable screen. A possible solution would…

Try this and let me know if it works: import com.atlassian.jira.project.Project Project project = issue.getProjectObject() def projectKey = project.getKey() def projectManager = ComponentAccessor.getProjectManager() def projectObj = projectManager.getProjectObjByKey(projectKey)

Hey @JacksonC , I suggest you post a new question to the forums (with a new subject line) as this thread has been answered. I am interested in the answer... Amir

Michael, can you expand on this please?

True, but the add-on is quite expensive just for printing a workflow. It's yet another case of having to take an expensive flight between two cities (=add-on) because the government (Atlassian) did not build a road between them...

To add an observation to this sub-discussion - Jira dashboard Pie Chart gadget does not support StatusCategory as a Statistics Type. Bummer.