Alexey Matveev Expert

You would need to add a scripted post function to the non engineering ticket type where you would find the related engineering issue type. You can see how to get linked issues here: https://community.atlassian.com/t5/Jira-questions/how-to-get-list-of-associated-issues-i-e-Issues-in-Epic-for-an/qaq-p/233060 Then you would…

I do not think you can add something to an event. Why you can not do everything you need in the listener for Issue A?

You would need an add-on for it like Power Scripts, ScriptRunner, Automation for Jira.

You could use Power Custom Fields add-on. It is a free add-on. https://marketplace.atlassian.com/plugins/com.keplerrominfo.jira.plugins.keplercf/server/overview

1. Power Scripts and ScriptRunner are basically the same. You would need to create global transitions to each status and name them as statuses. You could add a condition for the transitions so that they are invisible for users. You could call these transitions with the same name as statuses with a suffix ("_t")). Then you…

Maybe I did not understand your question. But you would need to make a rest call to get the info. GET /rest/api/2/issue/{issueIdOrKey}

I see. Then you do not have any add-on. You would need an add-on to synchronize subtask statuses with the status of their parent. For example, you could use Power Scripts, Scriptrunner, Automation for Jira.

You could search these issues in the Issue Navigator with a JQL query like this: sprint = "your sprint" order by status asc Then you could see all the issues with atrtibutes. 

How do you create a subtask? Do you use an add-on?

Hello, 1. You could use canned responses if you are on Jira Server/Data Center. Though you would need to choose manually a canned response upon entering a comment. 2. You could use Power Scripts Live Fields or ScriptRunner behaviours.

1. Log work button. Maybe it is not a core Jira log work button, but a Tempo work log button? 2. Workflow properties. You should make different workflows for issue types

The function will be like that: def findIssues(String jqlQuery) { def issueManager = ComponentAccessor.issueManager def user = ComponentAccessor.jiraAuthenticationContext.user def jqlQueryParser = ComponentAccessor.getComponent(JqlQueryParser.class) def searchProvider = ComponentAccessor.getComponent(SearchProvider.class)…

But you would need to do it all the time. Because sprints will be closed in the future.

I do not think it is possible out of the box. You should wirte your own custom field for it. You could use Power Custom Fields (it is a free add-on) or Scriptrunner.

You could use Web Fragments in ScriptRunner and create the Hide system or plugin UI element. If would look like this: Or you could use wokflow properties. You can find more info here: http://www.j-tricks.com/tutorials/permissions-based-on-workflow-status

Myabe like this !(issue.priority?.name == 'Priority 1' && cfValues['Test Phase']?.value in ['AAA','BBB'] && cfValues['Detected in release']?.value != null)

You can find such a script here https://community.atlassian.com/t5/Jira-Service-Desk-questions/How-to-change-default-tab-to-internal-comment/qaq-p/56715

You should use Select List (cascading). When you create the field there will be 2 fields created. You can set options for the first field and which options should be visible in the second field when an option in the first list is chosen.

Do you mean that you want to make internal comments by default? We found only one way to do it is to use JavaScript. But it is a bad solution.

try like this import com.atlassian.jira.component.ComponentAccessor import com.atlassian.jira.issue.CustomFieldManager import com.atlassian.jira.issue.MutableIssue import java.sql.Timestamp import com.atlassian.jira.event.type.EventDispatchOption def customFieldManager = ComponentAccessor.getCustomFieldManager() def dateCf…

This script worked for me import com.atlassian.greenhopper.service.sprint.SprintManager import com.onresolve.scriptrunner.runner.customisers.PluginModuleCompilationCustomiser import com.onresolve.scriptrunner.runner.customisers.WithPlugin import com.atlassian.jira.component.ComponentAccessor import…

You can find more info here https://community.atlassian.com/t5/Answers-Developer-Questions/Change-sprint-value-by-groovy-script/qaq-p/522895

Maybe it is a question of methodology. We plan only one sprint ahead that is why we do not need to know the whole backlog estimation. We make a higher level estimation of epics just to make sure that we are on time.

I do not know about a workaround.

GetChangeItemsForField returns a list of ChangeItemBean which contain the created date field. You would need to calculate who was the assignee in a certain status. You need to get all status changes and all assignee changes and build a matrix in your code which will tell you who was an assignee in a certain status. You can…

I believe that your Story points are summed up only for created sprints.

Kindly make sure that you have a version created in the project to which the issue belongs. https://confluence.atlassian.com/adminjiraserver/managing-versions-938847201.html

I think you should add a customfield which will let you distinguish if the issue was created from workflow A or independently. Then you could use this custom field in your condition. For example, let 's say you create a field called "createStatus". And you fill it with value 1 if it is created from the workfow A and with…

You can do it programatically. What add-on do you have? Power Scripts or ScriptRunner?

Hello, sub-task statuses are not connected with the statuses of their parent by default. That is why I guess you have some kind of setup in your Jira instance. You have to find it and deactivate. It must be an add-on.