Sorry, we don't support your browser.  Install a modern browser

Support Behaviours on sub-task issue types#103

As a ScriptRunner Admin,
I would like to set up behaviours on my sub-tasks,
So that I can apply my business rules to fields on sub-tasks

Pleaes comment with detailed use cases - they are very helpful!

2 years ago
Changed the status to
Gathering Interest
2 years ago

My use case is to fill in the description of subtasks of different types with different text templates to preserve the identity of the filling (necessary for subsequent automation)
For example, I have a task for developers, and our workflow involves creating a subtask for a team of technical writers. I need to fill in the description of this subtask with a table with certain headers that I will use later when parsing.

2 years ago

I need different expert teams wroking on the same story, so I have different sub-atsk issue types for each and I nee dto have pre-defined Description field to make sure all the required info is added to the sub-task.

2 years ago
J

We used this behaviour on premise but after moving to Jira Cloud it does not work anymore :(
We want to add templates to the description field

2 years ago
R

When on a JIra parent issue screen, in Jira Cloud, I have a use case where the Assignee for the Story and the Assignee for any Sub-tasks cannot be changes by the Dev/QA role. In addition, I also have a use case where the Dev/QA role cannot change the summary of the Story, but they CAN–and we want them to–change the summary of Sub-tasks.

5 months ago
G

When I create a story, I use behaviours in scriptrunner to assign a template and I use Atlassian rules to automatically create a few subtasks (at least one for Devs and one for QA), each of which need to have a template pre-filleds much like the parent card. We also use regression test card for which I use Behaviours to pre-fill the template in the description field but the sub-task cannot be pre-filled. I also use Behaviours for Epics and Task issue types. To be honest, Product owners are fine because they get both Story and Epic with their pre-filled description template, but QA is not because they have the lion share of the manual work to insert their template. Their cards are mostly sub-tasks to stories or regression issue types. So, currently they are out of luck. We don’t have developers to tackle the api levels but I dabbled in the Behaviours pre-canned scripts to create the desired template per issue type. And as a result, I am missing the Behaviours functionality for sub-task. That is a real bummer. You offer a service that is so valued but have not finished the job. We use many different types of subtasks: dev, QA, story bug, business QA, settings, vulnerabilities, architecture, compliance, etc. We have a complex set of workflows that use the company-managed projects with common processes to ensure moving cards back and forces across the many scrum teams. Not having the subtask template feature means ad hoc and inconsistent information being inserted in the various subtask types….we have about a dozen scrum teams in our division and many more divisions….

2 months ago
N

Why allow us to select subtask issue types in behaviors if they are not supported? If I need to make a field required, I cannot enforce on subtasks. Disappointing that this request is two years old and no movement.

a month ago