Amir Katz (Outseer) Expert

Thank you David. I tried the same code with a different cascading field and it worked. At that point I realized that the problem was not the JSON, but the values - the values that I have specified for the "problematic" field were not aligned with the context of the field - the values I was specifying are in context A, but…

To expand on a previous suggestion, here is how to do it with automation, without ScriptRunner: * Create two new number fields, CreatedAsNum and UpdatedAsNum * Add them to the issue screen(s), and move them to a new tab, call it Read-Only Fields* This way users will usually not bother with them * Not absolutely necessary,…

Notes about bulk change: * You're limited to maximum of 1000 issues at a time * You must have the necessary permissions in the project (assign issue, edit issue)* The actions you're presented which depend on your permissions

Thanks a lot to @Gideon Nolte _Eficode_ and @Vedant Kulkarni_Trundl who steered me in the right direction. The reason I was getting unaligned table rows is because there is a checkbox in the mail action in automation that says 'Convert line breaks to HTML line breaks' and is On by default. Once I set it to Off, the table…

Thanks, but there are 2 problems. First, I forgot to mention that I need borders and grid on the table. Second, this is what I get when I implemented your suggestion. #1 is the non-table, #2 is the table: What I need is two columns and a header row, like I described in my original question.

Aside from the 'validate' option (which is invaluable), if you have a Cloud Premium, I suggest you set up a sandbox instance, included with your premium subscription. Then you can test it to your heart's content until you get it right, then you perform the actual migration to your production environment. This is what I did…

@Yatish Madhav I cannot share the code, but I will share the algorithm in a blog post that I will publish soon.

I also share number 2 from @Kristján Geir Mathiesen 's list. Instead of waiting (forever) for Atlassian, I wrote a Python application that uses the Jira REST API to retrieve all CFs and then formats them nicely in an Excel sheet and makes it into a table, so I can sort the CFs by ID, name or type. I also added some…

As others have already said, you could use either a validator or a condition. Each has its own pros and cons and at the end, you need to make the decision.

@Monique vdB Thanks, I now have the edit button.

@Jimmy Seddon - When I click on the ... menu, I only see this:

Two minor comments: 1. JMWE is a paid add-on, but I find it extremely useful and worth its cost 2. I'm almost certain that the same functionality can be achieved with ScriptRunner (which we also have), but I have not tried that.

Just noticed the typo is the title, but there's no edit button... Come on, Atlassian, even Twitter now lets you edit tweets! Title should be Workflow validator to check if the assignee is not one of a list of specific users (uses JMWE)

Thanks for the answers, but adding .asNumber does not fix the problem. I have another project where a very similar automation works, so I have checked the differences. This 2nd project also has the date/time CF Event Started At, ID=11726, which is set manually by the user, before the automation rule is triggered. The…

Following up @Sue Wilson comment - for all CFs that have identical or very similar names, I went ahead and renamed them to make them distinct. I have not notified anyone about it. If this will break any filters, workflows or automations, I'm sure that I will hear from the affected people. So far - crickets... We even had a…

For the subject - I agree. Let me choose the features that I need, I don't really care what it's called. Do I need Kanban? Do I need Scrum? etc. For the underlying reason for this mess, I vote for reason 2 in @Arnd Layer's post. You can see it all over Jira - either teams do not communicate, or there is no top-level…

I had a similar situation - migrated two separate server instances to one cloud instance, ended up with approx. 1600 CFs. Since the Jira UI is sorely lacking in providing full information about CFs, I created a (fairly large) Python project (using Jira REST API) that retrieves all CFs and for each, checks whether it is…

True. Approvals is one of the differentiators that Atlassian pushes to convince people to pay extra for JSM...

I'm not confusing between the two, but you are correct about adding components - I'm an admin, so Jira lets me add components. Other users, non-admins, cannot do that. So I stand corrected, thank you.

Another option to consider is to add a post-function in the relevant transitions. * Unfortunately, Jira has a limited set of PFs for assignment. * Some add-ons (JEP, JMWE) provide their own PFs for assignment. * You can also roll your own scripted PF if you have either JMWE or ScriptRunner. Downsides: * You have to add the…

Regarding the solution using components, there are two problems (inherent to components): 1. Any Jira user can add a component, from the issue screen, so you may end up with "White Co", "White Corp" and "White Company". One small comfort is that the values are case-insensitive so you can't have "White Co" and "white co".…

In general, I try to stay away from groovy code as much as possible. They're difficult to debug & maintain and are not easy to parse for other people. If an add-on (such JMWE, JSU, ScriptRunner) or Jira built-in (automation) provides a functionality that does not require coding, I would prefer it.

If Planview Pro has any scripting and/or external integration capabilities, you may be able to integrate with Jira using the Jira REST API. But a simple search for the term 'integration' shows this document, and it includes Jira's logo:…

I also think that automation based on contents of a comment is too risky (e.g. a comment that says, "please do not approve this until I review it", could trigger the approval). IMO, Atlassian should add a new mechanism of approval without the need to add a status and transitions. Maybe they should add a new system field…

To add on @Alex Adland's reply - There is no 'transition screen' per se. On each transition, you specify which screen to display. The same screen can be used in create. Each screen has fields, and fields of type large text are rendered as defined in the project's field configuration that applies to the current project and…

Indeed this is a Jira bug. After working with Atlassian support, I was provided with a workaround, and an official bug was created: https://jira.atlassian.com/browse/JRACLOUD-79265 My two comments in the bug provide more details and explain the workaround. The reason that contexts were missing is that after the migration…

Also read up on smart values as they will let you combine data from multiple fields into variables that can be used in automation

Some updates: My original code uses the REST API call 'Get Fields Paginated'. It returns ALL fields, 1622 or so. When I perform the 'search issues', I use the field IDs that I get from the above call. So the first part of the error message ('field does not exist') is definitely not true here. So I added more code - a new…

I'm waiting for a few more answers here in the forum. If I don't, I will submit a support ticket to Atlassian.