Amir Katz (Outseer) Expert

As of Dec. 2021, we have moved our Service Desk project to the cloud. However, our portal users don't need the SLA, so we have not migrated this hack to the cloud. I can attest that the hack works - we wanted to display the assignee on the portal (which Jira does not let you do), so I created a field called 'Assignee…

@sergei_lavrov doesn't a cron job require an API token and REST-API code? Sounds a bit overkill to me. Also, the downside of using external systems (meaning outside of Jira) is that there's no trace in the project settings (automations, workflows, etc.) that there is an external mechanism (be it cron, Jenkins, GitLab…

I have not tried the solution that I have suggested (the JMWE post-function), but the post function is able to transition multiple issues, so you should try that. And please report back in this thread (assuming you do have JMWE).

If you're using the JMWE add-on (highly recommended), you can add a post-function in the 'Done' transition of the source issue. You use the JMWE Transition Issue(s) post-function, select which linked issue to operate on and which transition to trigger.

We've moved to the cloud, so most of the ScriptRunner stuff is n/a there. Regarding your need, I have a slightly different requirement (get data dynamically from another source), so I'm looking into the cloud add-on 'External Data for Jira Fields'. It seems that it can provide what you need.…

A quick question to the audience - has anyone tried this in Jira Cloud?

Adding my $0.02 here... 1. You can create a subtask under an issue only if the issue type of the subtask is included in the project's Issue Type Scheme (kind of obvious, but still worth mentioning) 2. If you use the Advanced Roadmaps feature (the 'Plans' in the top navbar), you get a different hierarchy which is unrelated…

All the hacks suggested in this thread will go away when Atlassian adds conditions to the Issue Create transition...

Using a validator 'if user is in role' does work, but the problem is that you cannot control the error message (it will be 'user is not in XYZ role'). What I did is use a validator provided by the JMWE add-on (not free, but worth the money) - the one called 'build-your-own (scripted) validator'. In it, I specified an…

One more observation, regarding the @Sergei Gridnevskii 's suggestion: I don't have inside knowledge of the Jira database, but I can speculate: 1. Text searches are the most inefficient as the values are not indexed 2. Any Jira entity that has a predefined set of values (components, select fields, fix versions, etc.) are…

This is a great suggestion, I was not aware of these two predefined fields.

Just to clarify: 1. Components are inherent feature of Jira and are not unique to JSM projects 2. You can add a post-function to assign the issue to project/component lead 3. Unlike labels, non-admin users cannot create components, which keeps the list controlled

Clarification and update: the problem is not specific to Kanban board in a JSM project but it applies to any Kanban board on a software project. I've submitted a bug to Atlassian support and will update this thread when I head back from them.

Hi @Markus , Thanks, this change indeed reduces the total number, but even after changing to 1 week I still have 55 issues, which I don't want to see. And I may be naïve, but I still expect the 'min' value to work... So I think it's a bug in the Kanban board.

Disclaimer: this is not really an answer... In Jira server, you could display error/info/warning popups using some Groovy code in workflow transitions - post-functions, validators and condition. It was part of ScriptRunner and JMWE add-ons which support Groovy code, but the Java functions for the popup were actually…

I'm facing a similar problem, after migrating to the cloud, but I'm not sure if any portal customer has received any notification. I've checked the settings as per @Alexander Bondarev and all looks good. Is there a way to debug this problem? And @Daniel Nile , did you open a ticket with Atlassian Support? 

@Sagar Mahajan your answer only applies to Service Desk Agents. If I try the helper (which is great, thanks for sharing), with a user who is only a Service Desk Customer, it says that she does not have the permission to view the issue. Which makes sense, since she only has portal access.

I've submitted a ticket to Atlassian support, ping me in private if you want to view it: https://getsupport.atlassian.com/servicedesk/customer/portal/48/PCS-69271

Thanks, @Ronnie Kingston , apologies (as I promised :-)). This is really cool and it's great that those extended options are provided (and documented) for advanced users.

does not work for me - dropdown is empty regardless of what I type. My JSM project is a company-managed, not team-managed (previously called 'next-gen').

This is a great tip. I do worry, though, that this is a hack workaround that relies on (I assume) an undocumented entity (_payload). What happens if OpsGenie changes this? If this is documented, my apologies - please provide a link to the docs. Either case, this mechanism should definitely be part of the integration…

no special characters. Project settings -> Request types -> <pick request type> -> Request form -> Visible fields -> hover to field, click in 'Field help', type text, click Update --> text disappears. I have no scripting-related extensions in my browser (Chrome latest).

Following up on @Piotr Stefaniak [HeroCoders] response, the epic copy functionality was spun off to a new add-on. This is from the 'Epic Maps for Jira' page: A previously available feature – cloning an Epic along with its stories, sub-tasks, and checklists has been deprecated and moved to Clone Epic for Jira.

Posted second part (custom fields): https://community.atlassian.com/t5/Jira-Software-articles/How-to-Find-Unused-Custom-Fields-in-Jira-Cloud-Using-REST-API-in/ba-p/1862039#M512

Posted first part (issue types): https://community.atlassian.com/t5/Jira-Software-articles/How-to-Find-Unused-Issue-Types-in-Jira-Cloud-Using-REST-API-in/ba-p/1862000#M511

Unfortunately, I cannot share the code, but I can share the algorithms... I will author a post instead of putting it here.

Another solution is to use a paid add-on. There are two that I'm familiar with: JEMH (Jira Enterprise Mail Handler): https://marketplace.atlassian.com/apps/4832/enterprise-mail-handler-for-jira-jemh?tab=overview&hosting=cloud JEMH connects to your mail server and monitors a specific inbox (e.g.…

I'm not sure what you mean by 'consolidation'. It can mean that you merge different schemes (e.g. permission schemes) and assign the same scheme to multiple projects and then delete the unused schemes. Same for other types of schemes - issue security, notification, screens, issue types, workflows, etc. Also, any unused…

An alternative that I used on server version (we have not moved our Service Desk project to the cloud yet), is to create a new field, make it visible in the portal and have some automation ( running in the background) to copy/update it from the SLA field. Since the new field is a custom field, it can be displayed in the…

Schemes is the way to go. But to manage those, you do need to use a CCB, or a dedicated project for Jira admins to ask for changes.