Ivan Tovbin Expert

Check out this documentation.

That's probably because your cutomers don't have the permission to share their requests with other people. To configure your customer permissions go to Project Settings -> Customer Permissions

I see. Well then I suppose writing a custom script which will send an email rather than using a built-in one is the solution here. This will also allow you to get the destination address directly from your select list which will dispense your from having to use any additional custom fields. Try this: import…

I take it you are using some 3rd party addon to send custom emails via post function?

From what I understand, your 'PagerEmailID-Text' is a scripted field. So the code is as follows: import com.atlassian.jira.component.ComponentAccessor def pagerEmailId = ComponentAccessor.getCustomFieldManager().getCustomFieldObjectByName("PagerEmailID") return issue.getCustomFieldValue(pagerEmailId).getValue() I'm not…

You can actually get a 'String' value of a single select list option. Can't you use that in you post function or am I missing something here?

Like Alexey has pointed out it's either Power Scripts or ScriptRunner. I suppose JMWE will work too.

Hi Stacey, First off an issue can't be assigned to multiple agents at once. There can only be a single assignee at any given time. That's by design. Surely, with some addons that enable you to use scripts you can pick your assignee conditionnally and/or randomly from, say, a specific user group, but that's about it. Now…

Also, please check if you can manually add attachments when your sub-task is in 'Closed' status. If you can't then it probably means that you don't have the permission to do so, while an issue is in that status. To check if it's indeed the case go to your workflow and check the status properties for your 'Closed' status.…

Can you post a screenshot of your transition screen?

Does the attachment itself get added to the subtask if you add it during the transition? Also, can you post a screenshot of your transition screen? Cheers.

Great, tell me if it'll solve your issue. Please keep in mind though, that this code assumes that: a) you add only ONE attachment during the transition and b) No other attachments are added as a result of this transition (either through automation or other post functions)

Hi Sergio, Based on your description, the attachment added during the 'Close issue' transition is always the last one (unless you have any post functions/automation that adds more attachments after that), the code to copy it to the parent issue is as follows: import com.atlassian.jira.component.ComponentAccessor def attMgr…

Based on your description, the attachment added during the 'Close issue' transition is always the last one (unless you have any post functions/automation that adds more attachments after that), the code to copy it to the parent issue is as follows: import com.atlassian.jira.component.ComponentAccessor def attMgr =…

Hi Germain, I might be able to help you here. Can you please clarify, if you want to copy just the attachment that has been added during the 'Close issue' tansition, or all attachments (including this one) that has been accumulated in the sub-task up until this point?

Hi Lukasz, I think you should bring this issue up with Atlassian Support.

Hi Raz, a) Yes, this can be done. You can create an automation rule, which will trigger on 'Issue created' event and if the issue matches a proper JQL then it'll set the priority to, say, 'Critical'. A JQL for this can look something like this: Summary ~ "Urgent" OR Description ~ "Urgent" b) Can you give more details on…

Hi Jan, An issue cannot be assigned to a group of users by design. Only a single user can be an issue assignee at any given time. That said, I suppose that with some scripting (using addons like ScriptRunner or JMWE) you can automatically set an assignee conditionally or randomly from a specific user group. You can also…

Hi Mosh, From Bitbucket Cloud Pricing FAQ: Can I buy an annual subscription? Annual subscriptions are currently not supported on Bitbucket Cloud. 

Hi Rodolpho, Here's how you do it: 1) Create a new report. 2) Add an "Average rating" type series to it and apply a JQL filter to it: Organizations = "organization name" 3) Add more series' for other organizations.

Great points, David, cheers for the feedback! And yeah, totally forgot about hiding the transition.

Hi Martin, Not out of the box, no. However Email This Issue addon can easily do it.

Hello, We've had a similar problem and here's how I managed to solve it. Basically, what you do is if the reporter and approver is the same person then you simply make your issue skip the approval status. And since you have JMWE (from what I understand) it's super easy. Let's say your workflow looks like this: status 1 -->…

Hi Mosh, Not exactly. You can actually have as many users registered in Jira as you like. You license tier only dictates how many users can be given application access. More info in this documentation.

Here's how you do it. def currentUser = ComponentAccessor.getJiraAuthenticationContext().getLoggedInUser() def linkMgr = ComponentAccessor.getIssueLinkManager() linkMgr.createIssueLink(11111, 22222, 33333, 1, currentUser) /*where 11111, 22222 and 33333 are source issue id, destination issue id and issue link type id…

'Closed' status is generally used to review the resolution. If the reviewer (QA staff, reporter, superviser etc.) is satistifed with the resolution then he proceeds to close the issue or reopens it otherwise. If your process does not involve anything like this you can safely remove this status. You can always add it back…

Hi Andrei, This is because when you passed the ticket to another team, the ticket remained within the same cycle of the same SLA metric. I see two options to solve this: 1) Provided your issue enters a new status when you change support levels you can configure your current SLA metric to stop when an issue enters that…

Hi David, Sure you can. One would think that this JQL would work: "definition of done" in (option1, option2, option3) But it won't because it'll return all issues that have at least one of those options checked or any combination of those options. So if you want to return issues with specific options checked you need to…

No no, you are mixing up two different sections of your project, 'People' and 'Customers' that is. Check out this screenshot:

Hi Ricardo, I think this documentation is what you are looking for.