Hi All,
We are planning to use Jira for our complete development process and not only for issue/task tracking. This would require that we create structured jira issues.
I am looking for a functionality which does the following:
Once the user creates an issues for tracking a new feature, predefined subtasks and/or subissues are created and linked to the parent task.
Our structure might look like this
Feature
- Implementation Task
- create jUnits Task
- Knowledge Transfer Task
- create Testcases Task
-etc.etc
if somebody has an idea on how to do this automatically or knows a plugin or has an better idea to do such a Feature planning/tracking, please let me know
THanks in advance,
Patrick
There are a lot of Groovy scripts posted in the previous forums to do this, but the easiest way is to use the Script Runner built-in script called "Create a sub-task". You'd invoke this as a post-function in the appropriate workflow transition.
Thanks,
seems that this is what we are looking for, need to dig into this scripting though
Patrick
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Almost no coding should be necessary.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
BetsyW & Jamie,
we are trying to set the summary of created subtask to be the summary of the original issue (the parent) plus some additional test.
We tried to add some ccode to the field "Additional issue actions):
issue.summary = originalIssue.summary + 'Create Feature Fact Sheet'
This fails with some errors, it seems that originalIssue is null.
Can you let me know how I can access the parent issue when e.g. creating a subtask?
Thanks
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
The summary will be set to the parent's summary by default, so you can do:
issue.summary = issue.summary + " Create Feature Fact Sheet"
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Jamie,
that works as you described. But is there a possibility to still access the parent issue somehow. We want to pull out information from parent issue fileds and want to add (or combine them) them to other fields of the newly created subtask.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
All of the applicable custom fields are also copied over by default, however the original issue is available in "transientVars.originalissueobject". I meant to make this easier but somehow I didn't.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks Jamie,
that`s it!!
btw, great plugin, helps a lot to setup our processes
Patrick
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
We use a customized version of https://studio.plugins.atlassian.com/wiki/display/CSOT/Jira+Create+Subtask+for+transition. This has proved to be quite flexible and handy.
Edit: Now shipped as JIRA Create on Transition Plugin
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello Bob, we are using Jira 4.3.x, so CSOT seems not to work
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I will look into posting an update that works for 4.2/4.3/4.4.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Updated plugin now referenced in the answer.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.