Tarun Sapra Community Champion

Please see some samples here https://scriptrunner.adaptavist.com/latest/jira/listeners.html#_custom_listeners Also, you can use a built-in listener (send custom email) to send notifications to required people. https://scriptrunner.adaptavist.com/latest/jira/listeners.html#_built_in_listeners

Hello @vidoq You can create script listener, which checks if the issue created/updated has an epic or not. And if the updated issue has an Epic then update the required fields of the Epic.

Hello @Eugene Dementiev Yes, I can understand why it's required, as I have implemented something very similar to your requirements in the Jira server version using Script runner plugin 's scripted fields. 

When viewing the sub-task you do see the parent's issue key in the listing, the issue key of parent is listed just before the sub-task's issue key

Hello @Eugene Dementiev Having the parent reference of a sub-task visible in the issue navigator view is an open ticket https://jira.atlassian.com/browse/JRACLOUD-16589

Hello @Michael Buechele As to why it's not supported, this can be best answered by someone from Atlassian only. Here's the roadmap for next-gen projects https://www.atlassian.com/roadmap/jira-software You can continue to use classic boards if you feel next-gen projects lack the features you need. Once the next-gen projects…

Hello @Michael Buechele Thanks for the screenshot, now it's clear. Currently, its not supported, may be in the future. See ticket here https://jira.atlassian.com/browse/JSWCLOUD-17268

Also, please note that "Epic link" field is only available for issues which are added to epics in the epic view by clicking on the "plus" sign. If you have a sub-task added to an epic it will never show the epic link in the issue view of itself because the relationship between sub-task and epic is that of parent-child…

If you see in the above screenshot, it lists the fields which we can configure (including certain types of custom fields) but there is no epic link field which can be added on the story or on the sub-task

Hello @Eugene Dementiev Currently, epic link custom field doesn't seem to be available for the issue types in the next-gen projects nor is the field supported by next gen projects https://jira.atlassian.com/browse/JSWCLOUD-17239 https://jira.atlassian.com/browse/JSWCLOUD-17389

Hello @Michael Buechele I just checked on cloud instance, now the Priority is available. You can add it like Project settings -> Issue types > (select the correct issue type) List of fields is now available and you can add priority field and then click on "Save changes"

Hello @Michael Buechele As per the Atlassian's post about this Basic custom fields Create custom text, number, date, time, and label fields for your project's issue types. Required fields, default values and more custom field types and options coming soon. Priority and resolution per project is coming soon. Complete post…

Hello @Steffen Becker I did some testing on my end and here's what I found The method "getAssociatedIssueTypes()" for FieldConfigScheme always returns NULL irrespective of associated projects or no associated projects. I don't know why it always returns null but that seems to be the case. I am using 7.11 version of Jira.…

Hello @Steffen Becker Thanks for sharing the screenshot, just a hunch, I feel that the method "getAssociatedIssueTypes" is returning 0 because "getAssociatedProjectObjects" is returning 0 , i.e. the method "getAssociatedIssueTypes" returns only the issueTypes which are actually part of an scheme which is associated with an…

Can you please share the screenshot of the exact code and the console output. Because it's hard to beleive that the issueType scheme contains the issueTypes yet it's displayed as 0 in the logs. schemeManager.getAllSchemes().each { print it.getName() // here you can check if you see the name of all the issueTypeschemes and…

Hello @Steffen Becker Did you try adding logging and see whats getting printed or try the code in the script console try{ if(it.getAssociatedProjectObjects().size() == 0 && !it.isGlobal()) { sb.append("${it.name}") // print the contained issuetypes it.getAssociatedIssueTypes().each { //print here it.getName() } } }

Hello @anthony_butler You can have Jira gadgets(based on JQL filters) added on Jira dashbaords which refresh automatically thus always showing the real-time information. https://confluence.atlassian.com/jirasoftwareserver079/configuring-dashboards-950291323.html…

Hello @Emilio Colangelo If the issue is fixed, please accept/upvote so that other users are also helped!

Hello @Fazila Ashraf Just remove the transition screen from the transition and in this way only the post-function will set the resolution and users will not see the transition screen. See here as to how you can access resolution…

https://confluence.atlassian.com/servicedeskserver0313/managing-access-to-your-service-desk-952617828.html

https://confluence.atlassian.com/servicedeskserver0313/permissions-overview-952618691.html

Hello @Emilio Colangelo The users should be part of the below role as per the docs Browse Projects Service Desk Customer - Portal Access Project Role (Service Desk Team) Project Role (Administrators) Permission to browse projects, use the Issue Navigator and view individual issues (except issues that have been restricted…

Please see this open ticket https://jira.atlassian.com/browse/JRACLOUD-69237

Hello @Luna ZHANG On the cloud the ability to add new fields to issue detail view screen is very less as compared to server, so as per the URLs I have shared with you if you can't add acceptance criteria on the issue details view on cloud then currently it's not possible.

Hello @vicky kung For performance, you would need to see the lgos, monitor CPU, memory, cache usage, there is no special plugin for this purpose. "I want to ask a question that whether this plugin can calcute a field before a month ?" Please raise a separate question.

https://jira.atlassian.com/browse/JRASERVER-16281

Hello @Natalia Lezhai Currently it's not possible to define the order of linked issues. Here is the open ticket, feel free to vote on it https://jira.atlassian.com/browse/JRACLOUD-16281

Hello @oks In order to hide the field you should code cField.setHidden(true) But you are writing cField.setHidden(false)

Hello @oks When you add a behaviour to a field then the script is triggered when the field is changed. But in your case your hiding the field only when the status changes, thus your script should be triggered on the status change and need not be linked ot the field. My suggestion to you is to add the script in the…

So you can create a filter like (issues due in next 5 days) duedate < startOfDay(5d) and duedate > startOfDay() This gives issues with due date in next 5 days, and you can have a subscription around this filter.