
1667 Workflows for bugs that follow standard life cycles and options that uses Scriptrunner and postfunctions
1667 Workflows for bugs that follow standard life cycles and options that uses Scriptrunner and postfunctions
1667 Workflows for bugs that follow standard life cycles and options that uses Scriptrunner and postfunctions
More details
This is a quick bug workflow process that incorporates Scriptrunner and post functions to effectively manage a bug life-cycle.
This assumes that the QA process is integrated with the primary development process and encourages collaboration directly with all those involved. Primary control of the workflow is done via the QA organization.
Reviews for cloud
(0)Sign in to write a reviewReviews for server
(0)Sign in to write a reviewReviews for Data Center
(0)Sign in to write a reviewCloud Pricing
Server Pricing
Data Center Pricing
This app is sold by a third-party vendor.
Let us know that you'd like to manage this app's billing on your Atlassian invoice.Pricing FAQ
- What does 'paid-via-vendor' mean?
Paid-via-vendor apps are licensed and purchased directly through the vendor who makes this app.
Payment for paid-via-vendor apps is not handled by Atlassian.
- Will paid-via-vendor transactions be on my Atlassian invoice?
Paid-via-vendor transactions are not managed by Atlassian. This means transactions for paid-via-vendor apps will not be on your Atlassian invoice.
Basic support resources are available for this app.
Vendor support resources
Find out how this app works.
Atlassian-hosted discussions connect you to other customers who use this app.
Versions
Version 1.0.0 • Jira Server 8.9.0 - 8.9.1 • Released 2020-06-11
Summary
First Version