Ivan Tovbin Expert

Here's how you do it: import com.atlassian.jira.component.ComponentAccessor import com.atlassian.jira.issue.label.LabelManager def currentUser = ComponentAccessor.getJiraAuthenticationContext().getLoggedInUser() def cfMgr = ComponentAccessor.getCustomFieldManager() def country =…

Hi Kevin, Try this: chgHistMgr.getChangeItemsForField(issue, "Link").findAll{it.getTo().contains("PC-")}.collect{it.getCreated()} This'll return an array of Timestamp objects, each of which represents the time when your issue has been linked to a "PC-...." issue. After that you can use an element from this array (a…

Hi Chase, The difference between a free-text custom field and label custom field is that the former contains a string and the latter contains an array of Label objects. And so you need to treat these fields accordingly when setting their respective values. As per LabelManager Interface documentation, addLabel method seems…

Please mark this soultion as "Accepted" if it resolved your issue.

Unfortunately not. It'll simply return all issues that ever had this status, but it won't show you who the issue was assigned to during that status.

For example, try: created >= startOfWeek() and assignee = currentUser() This will return a list of issues created since the start of current week and assigned to the current user. If you want to know the date of assignment, then there is no such thing in Jira out of the box. However, you can create a 'date' type custom…

Ah, I see. You can configure as many different request types as your heart desires. You can add different fields to your request types for your customers to fill out. Your customers will be able to track their open requests through the customer portal.

Hi Marc, Columns in Filter Results gadget represent various fields of the displayed issue. Since parent summary is not a field there is no way to display it. However, using 3rd party add ons like ScriptRunner or JMCF (free) for example, you can create scripted fields which will contain the current value of a parent's issue…

Hi Robert, 1) Yes, Jira can have different workflows associated with different issue types. Keep in mind though, that you can have a single workflow cover a number of issue types, but you can't have an issue type associated with multiple workflows at once within a single project. 2) Customer portal is a standard feature of…

Hi Ken, I assume that by label you mean "Status". Status names have nothing to do with the buttons you see on your issue view screen. Those buttons actually represent workflow transitions (arrows between statuses). With that in mind, if you want to rename your button, you have to rename a corresponding transition. Hope…

Hi Chegg, I think this can be done if you use this JQL for your filter: status was in ("Under Review") or status = "Under Review" For your "Rejected" and "Cancelled" statuses you'll have to set up separate filters using a similar JQL. 

Check your global permissions. Go to Administration -> System -> Global Permissions and check who has the permission to 'Create Shared Objects'. Perhaps your user does not. If that doesn't help check your browser console for any errors when your user loads up 'Edit permissions' screen of his filter. Hope this helps.

Hi Charles, Given that with proper permissions one can create any group with any name and give it any permission it's pretty hard to tell the difference between two groups just by looking at their names. For all we know there might be no difference at all! But first things first. I'd start with checking global permissions…

Check out this documentation on searching for issues in Jira. Hope this helps.

Ok. To delete an issue click on "Delete" from the issue's "More" menu: If you don't have that option in the menu, then it probably means that you don't have the permission to delete issues. To check that go to Project Settings -> Permissions and look for 'Delete Issues' permission.

Please mark the solution as 'Accepted' if it resolved your issue.

@ariel alonso Please advise if you are on Server or Cloud?

To delete issues you (or a group/project role you belong to) need to have the "Delete Issues" permission in your project's permission scheme. 

Hi, Check out this documentation.

Hi Wojtek, There's a couple of ways to do this: 1) Create a scripted post function that will set an assignee depending on your custom field value. This will require a 3rd party addon like ScriptRunner or JMWE. 2) Create an automation rule that will trigger when your issue is transitioned and set an assignee based on your…

Hmm, that's odd. Both updateIssue and updateValue work for me just fine. Perhaps there's something wrong with your code? Try this: import com.atlassian.jira.component.ComponentAccessor import com.atlassian.jira.issue.UpdateIssueRequest def currentUser = ComponentAccessor.getJiraAuthenticationContext().getLoggedInUser()…

If you are talking about Automation for Jira addon, then I'd say you need two separate rules. The reason you are getting this error is most likely because the supposed parent issue does not exist yet when the rule is triggered (not run!). When Automation for Jira rules are triggered they are placed in a sort of queue…

"I find your lack of faith disturbing" A gem of a line!

Can you explain what are you trying to achieve exactly?

Hi Jeff, There are a couple of options here: 1) You can add your CRM email to 'Request participants'. This will ensure that every single notification which is sent when a public comment is added to an issue by either your customers or your agents will also be sent to that email. Request participants can be added either…

Hi Marzi, I think issue security might be the thing you are looking for.

Hi Germain, This is totally doable actually. Please keep in mind a few things though: 1) The validator checks temporary attachments (files which are added on your screen but not yet uploaded to the issue) against attachments in other subtasks, and if a match is found (I've added not only a filename but also a filesize…

I'd suggest contacting add on vendor for that. Perhaps it might be a bug.

Try wrapping your code in this closure: if (event.issue.getProjectObject().getKey() == "your project key"){ }

Hi Frank, Just in case you still wanna use a script to do it, here's how: import java.sql.Timestamp issue.setDueDate(new Timestamp(System.currentTimeMillis()))