Workflow definition to auto-create followup task if needed

[sniederb]

In our development process, our customers receive a software artefact for testing along with a list of JIRA tasks included in that artefact. The customers can then verify that the changes are according to their needs. They get JIRA tasks in the status "Resolved", and can either "Accept" or "Reject" the task.

The "Reject" action leads to a re-open of the task, which is cause for discussion. As the software changes associated with the task were delivered with the artefact, a re-open seems counter-intuitive, as there is really no option to eg. set the task to "won't do".

We'd much rather have an automatism where a "Reject" asks for a comment, and opens a follow-up task with that comment as description, and high priority. The original task should be closed. Does JIRA - or possibly a JIRA plugin - offer such a workflow?

Thanks
Simon

[Bryan Trummer - ReleaseTEAM]

Hi @sniederb - There are a couple of ways you could achieve this. In the workflow for Reject you will want to have a screen for that transition that has the comment field (any screen displays the comment field). That reject transition could go to whatever "final" status you want it to be in (Rejected or whatever your team deems makes sense). As part of that Reject transition there are a few plugins in the Marketplace that do provide creating a new ticket via a post function. We do this today in a few of our projects.

Take a look at the following apps as they both provide creating an issue as part of the workflow post function. I would suggest testing and seeing if they fit your needs.

Create on Transition by Bob Swift, and JIRA Suite Utilities for JIRA.