Parallel Status workflow for sending customers beta versions?

[eirens]

Jira Cloud

We use the following Statuses right now:

• Open
• In Progress
• Resolved
• Verified
• Closed
• Reopened

Those are working well for us.

But we want to be able to use transitions/workflows for Tech Support personnel to request permission to send a beta to a customer. Such as by setting a "Beta Requested" Status with a transition probably named "Request Beta".

I'd like development staff (product manager) to be able to approve or disapprove the beta request by changing the ticket's status from "Beta Requested" to "Beta Approved" and then have the SUpport person transition that to "Beta Sent".

But I don't want any of this to replace Resolved and Verified values in the issue's Status.

The reason I don't want to just use a pull-down custom field for this is I want a box to pop up during certain these transitions so we can pick which beta version to request, which beta version to approve, and maybe even have Jira automatically store the beta sent date (current date of "Beta Sent" transition event) in a custom date field.

I want this stuff automated and lightweight for users.

So is there a way to have a parallel workflow/transition pathway?

[Mikael Sandberg]

An issue cannot be assigned to multiple statuses at the same time. I have a project with a similar scenario and the way we solved it was to use subtasks that follow a different workflow. 

[eirens]

Thank you.