Ivan Tovbin Expert

You are doing it almost right. You need to check that this is NOT a 'Create' transition: if (getAction().getId() != 1){ ..... } 1 is always the ID of 'Create' transition. 

Behaviors could be the solution, but it'll require some fine tuning, like specifying actions (screens) where you want 'Summary' to be editable for everyone (like Create screen). Other than that I don't really see a problem with behaviours. Please let me know if you need help with the code.

Indeed, my mistake. I've updated the code above. You can ignore the warning on line 16. Also please make sure that you place this post function LAST in the post function list in your transition.

Hi Mahdi, There's a way to achieve this. Not the most elegant solution, but it works. 1) Remove 'Summary' field from issue 'Edit' screen 2) In your workflow create a GLOBAL transition, that lead to ITSELF. That way it will be available in every status, but won't change the current status once used. 3) Add a screen to that…

Hi Lukas, Assuming this is a postfunction for your "parent" issue, here's the logic (if I understood you correctly): 1) Find an issue linked to your "parent" through "Vykazovanie" link type 2) If such issue is found, check if it belongs to ESMOSV project 3) Copy that issue's assignee to parent's "Technik" field The code is…

Hi April, As blunt and simple it might sound but at least for testing purposes have you tried adding a post function to you sub task "Create" transition, which would fire a custom event. And then reconfigure your listener to listen to that custom event. If you place this post function LAST on your "Create" transition, then…

I suppose you could create a collection of queries and then iterate through it in a cycle and run a search using each element (query).

Hi Chris, First off I'd start with configuring proper handlers for your HttpBuilder. That way you you'll always be able to see what is wrong instead of simply getting an exeption thrown at your face. I wrote this simple method to create an instance of HttpBuild with all handlers configured: import…

Hi Eric, Frankly I didn't quite get what exactly you are trying to achieve, however I'd start with optimizing your code a little bit: import com.atlassian.jira.bc.issue.search.SearchService import com.atlassian.jira.component.ComponentAccessor import com.atlassian.jira.issue.IssueManager import…

Hi @Sam Morris Thing is, after you call any setter method from MutableIssue interface (that would be setCustomFieldValue() in your case), you need to update that issue to persist those changes into the database. Here's how I do it usually: import com.atlassian.jira.component.ComponentAccessor import…

Yes, as long as those projects are within a single Jira instance. If not you'll have to use REST API to access issues from another Jira.

Hi @Bartlett, Leigh , Out of the box I don't think it's possible. The first solution that comes to my mind is to use Email This Issue add-on. It allows you to configure custom email templates and then use those templates in workflow postfunctions to send emails.

Good practice would be to put your users in groups and then simply assign groups to project roles. Other than that, you can either do it manually, after all 40 users is not really that much. Another approach would be to move them with a script. You'll need a 3rd party add-on like Scriptrunner or JMWE for this.

This can't be done out of the box. Scriptrunner behaviours can do it to a certain point. You can't use behaviours on 'View' screen. On all other screens you can hide this field conditionally using behaviours. You might as well consider this add-on: Field Security Plugin for Jira

Hi, @Shawn Danisa Make sure your imports look like this: import com.atlassian.jira.event.type.EventDispatchOption import com.atlassian.jira.issue.MutableIssue import com.atlassian.jira.issue.link.IssueLink; import com.atlassian.jira.component.ComponentAccessor;

@Vineela Durbha Check out this article: https://community.atlassian.com/t5/Agile-articles/Three-ways-to-update-an-issue-in-Jira-Java-Api/ba-p/736585

Hi, Could you please clarify: 1) How exactly this script is supposed to be used? Is it a listener, a post function? 2) If this is a listner, wouldn't it be better to have it trigger on a custom event, which will be thrown by your transitions? That way you can grab all the necessary field values directly from the issue.

I'd use Scriptrunner to write a script to check subject and/or body against a regex and then set due date based on the results.

Use this JQL: creator in (username1, username2, username3)

Hi, Can you confirm that when a fix version is set via your script, this change is reflected in your issue's change history?

Hi Laurent, When you clone an issue you basically create a new issue, whilst copying all field data from your original issue. Since you create a new issue it is natural that it gains the status your 'Create' transition leads to. With that in mind, if you want your clones to gain the same status as your original issue,…

Hello, Indeed, a scripted validator is the solution. Here's the code: import com.atlassian.jira.component.ComponentAccessor import com.atlassian.jira.issue.Issue import com.atlassian.jira.issue.customfields.option.LazyLoadedOption import com.atlassian.jira.issue.fields.CustomField import…

Searching through the Marketplace, I think this might do the trick: https://marketplace.atlassian.com/apps/1219043/meeting-mate?hosting=cloud&tab=overview&_ga=2.149384438.1744553609.1549970607-1741309663.1548425436

You can't make a scripted field mandatory because a scripted field is read-only by design. Users are not supposed to be able to enter its value manually.

Hi @Ole Markus Pedersen, Could you please clarify, 'Location' is a custom field or a user property?

Hi, Please check out this documentation.

Hi, You do it like so: import com.atlassian.jira.component.ComponentAccessor import com.atlassian.jira.event.type.EventDispatchOption import com.atlassian.jira.user.ApplicationUser import java.sql.Timestamp ApplicationUser currentUser = ComponentAccessor.getJiraAuthenticationContext().getLoggedInUser() Timestamp…

Hi, I'm afraid not. As per this documentation users must have Jira Administrator global permision to be able to do so.

@Evgeniy Buturlia I suppose something like this should do the trick: import com.atlassian.jira.component.ComponentAccessor String baseurl = ComponentAccessor.getApplicationProperties().getString("jira.baseurl") String issueUrl = "${baseurl}/browse/${issue.getKey()}"

@Gonchik Tsymzhitov We've been usuing IMB Notes 9 so far, but are looking at MS Exchange right now. Didn't really have any problems with either.