Ivan Tovbin Expert

@Gonchik Tsymzhitov We pass "text/html" to setMimeType() method and simply use HTML tags in email body, like so: setBody("<font face=\"Calibri\" size=\"3\" color=\"black\"><b>some text:</b> <a href=\"$baseUrl/browse/$key\">ABC-123</a>some text<br><br><b>some text</b> some more text<br><b>some more text</b> some…

Assuming your custom field is IN your sub-task (and not in its parent issue for example) the code would be as follows: import com.atlassian.jira.component.ComponentAccessor import com.atlassian.jira.event.type.EventDispatchOption import com.atlassian.jira.user.ApplicationUser ApplicationUser currentUser =…

@Callum Carlile _Automation Consultants_ Sure thing. Please advise your custom field type and when do you want this to trigger? Cheers.

Hi, This is where you have a problem: def emailAddress = issue.getCustomFieldValue(customField)?.get("1")?.value Assuming your "Requirement Owner" is a single-userpicker type field, it's value is an ApplicationUser object. With that in mind here's how you extract email address from ApplicationUser: String emailAddress =…

Ho Joshua, Perhaps this'll help? https://docs.atlassian.com/software/jira/docs/api/7.6.1/com/atlassian/jira/event/fields/layout/FieldLayoutSchemeUpdatedEvent.html

Here's how you do it: import com.atlassian.jira.component.ComponentAccessor import com.atlassian.jira.issue.Issue import com.atlassian.jira.issue.IssueManager import com.atlassian.jira.issue.comments.Comment import com.atlassian.jira.issue.comments.CommentManager import com.atlassian.jira.project.Project import…

Here's how you do it: import com.atlassian.jira.component.ComponentAccessor import com.atlassian.jira.issue.Issue import com.atlassian.jira.issue.IssueManager import com.atlassian.jira.issue.comments.Comment import com.atlassian.jira.issue.comments.CommentManager import com.atlassian.jira.project.Project import…

I see. It seems a scripted post function is the solution here. Here's the code. Use it for a scripted post function on a transition which is used to move a ticket to 'Done' status: import com.atlassian.jira.component.ComponentAccessor import com.atlassian.jira.issue.AttachmentManager import com.atlassian.jira.issue.Issue…

oh, Jython. I thought you had Scriptrunner. Unfortunately i'm not familliar with Jython, but looking at your original code I see at least one mistake. In your 'if' statement change 'getName()' method to 'getValue()' and see if that helps. Or if you have Scriptrunner, use that instead and use my code for it.

To narrow down the list of possible reasons for this behaviour, if you remove the validator for your 'Create' tansition, does it allow you to create issues after that?

Can you please give me more info? What does it say? Does it let you transition your issue? What is the value of your custom field when you are trying to transition your issue? Cheers.

Hi Olivera, It appears that you are trying to write a scripted validator, yes? Here's what you need to fix it: import com.atlassian.jira.component import ComponentAccessor import com.opensymphony.workflow.InvalidInputException def value =…

Sure thing. When exactly do you want this to trigger?

Hi Lauren, I'm afraid you can't do this with basic jira functionality which is available out of the box. You'll need 3rd party addons like Scriptrunner, Power Scripts or Automation for Jira to achieve this.

You can't. Fields with no value in them are not displayed on issue view screen. 'None' is not actually a value, it's an indication that a field has not value. That's how Jira works right now. There's an open feature request for this, feel free to vote and follow.

No, not really. Basically what you'll do is fetch the value from the issue itself if it's NOT a subtask. If it is, then it first finds its parent, and then fetches the value from there. Incidentally, in your setup, is there always ONE subtask per parent issue? Hope this helps.

Hi David, Have you tried to re-use your scripted field A in your sub-task, and simply modify the code to check for current issue type. If it's a standard issuetype, then grab your custom field values from it, if not, then grab them from parent. I think it'll take a single line of code to modify it: def issue =…

Hi Paul, While it is technically possible to exclude select users from recieving notifications, in reality it means that you simply have to add all users that HAVE TO recieve these notifications. Jira does NOT allow you to exclude users in a notification scheme. So instead of excluding some users that don't need a…

Hi Todd, By default request participants are allowed to add comments to issues. It seems that in your case however something is preventing them from doing so. Here's a list of things to check that may help you troubleshoot this: 1) Check you mail channel log to see if there are any errors while emails from your request…

We are using Scriptrunner to create issues on a schedule from various templates and assign them conditionally to different people.

Try this: issuetype = Bug AND creator in membersOf("group name") AND status = Resolved AND (resolution CHANGED BY x OR resolution CHANGED BY y OR resolution CHANGED BY z) Not the most elegant query, especially if you have lots of resolvers, but I'm afraid there's nothing else you can do here with what's available in Jira…

Hi, The short answer is - yes. Check out these documentations for more details: https://confluence.atlassian.com/adminjiraserver073/managing-project-roles-861253314.html https://confluence.atlassian.com/adminjiraserver073/managing-project-permissions-861253293.html

@Doğucan Baskın I suppose it's quite possible with Automation addon. You need to create a date picker custom field and them populate it with Automation. You might need to use math functions that Automation supports, to calculate the resulting value for your field.

Hi Kelly, Go to Admin -> System -> General Configuration. Click on "Advanced Settings" and find "jira.clone.prefix" property there. Remove the value from that property and voila! Your clones, whether it's a parent issue or a subtask will not have a "Clone" prefix added to their summaries when created.

Hi Jason, While I'm not familliar with Butler Bot for Trello, it is my understanding that it is used to automate processes inside your Trello instance. Now as far as I know there's no Butler for Jira, however there's a wide range of 3rd party addons that allow you to configure all sorts of automation. Check out this…

Hi Russ, An issue can have only one assignee at any given time. That's by design. Could you describe your usecase? Perhaps I could advise you on some workaround. Cheers.

Hi Alexandra, The proper way to "close" or "archive" a project is simpy to restrict all access to it. This way you'll keep all old issues and all historical data and at the same time prevent the creation of new issues. I'd like to stress that deleting a project is NOT a good idea. If you need to migrate some issues from…

Hi Jerry, When you clicked "Publish", Jira prompted you to create a copy of your old workflow, before publishing your changes. If you haven't done that, then I'm afraid that you can't restore your previous workflow.

Hi Avidan, I'd create a JQL filter and have all interested parties subscribe to it. The JQL I'd use would look something like this: updated < startOfDay(-3) AND resolution IS EMPTY This'll return all unresolved issues, which have been updated 3 days ago or earlier. 

How does Jira know that a person is on leave? When do you want this automation to happen?