This is a guest blog post submitted by Vincent Thoulé. Vincent started his journey with Jira by implementing CMMi in IT services for a European Bank. After 4 years of committed work on Kaamelot, in 2009 he accepted to join Pyxis Technologies in Montreal in order to continue the Jira adventure on a full-time basis.
This is the second post in a 3-part blog series about Minyaa. The first post is an introduction to using Minyaa for time tracking.
Minyaa is proud to announce that an upgrade is now available, Minyaa 2.2. Check out the release notes.
Initially dedicated to expanding Jira’s worflow capabilities and simplifying workflow design, Minyaa Workflows has been born anew with the integration of the Workflow Designer with Flex.
Minyaa Workflow Designer now gives visibility of OSWorkflow concepts:
- Common Transitions
- Global Transitions
- Recursive Transitions
The best ways to learn about Workflow Designer:
- Watch the following video (2:32) to see the default Jira workflow re-created using Minyaa Workflow:
Your browser cannot play this video. Learn how to fix this.
- For a more sophisticated example, see how we use the workflow optimization to reduce a workflow’s transitions from 141 to 21!
Another great feature that’s provided is the Automatic Transition. This service provides a way to automatically perform workflow transitions when specific criteria are met. It is a way to include some conditions for Workflow Transition based on time without having to develop a dedicated Event Listener or complex Jelly Script ran as a Service.
The solution is based on:
- A set of conditions provided to:
- reserve transitions to a technical account
- evaluate time events:
- Has an Issue been edited or commented in a defined delay
- Has a Time Spent been logged in a defined delay
- Has a Transition been executed in a defined delay
- Is a date reached?
- An auto transition service able to execute a Workflow Transition when defined conditions are met for an issue
- Is an Issue (in a specified Issue Type) similar to the current Issue?
- Yes, then I am able to link it with the predefined Issue Link Type
- No, then I am able to clone partially the current Issue then link it
- The combination Source Issue / Target Issue are defined in scheme applicable per Project.
- In the current Clone operation, a automatic mapping is done only for the same fields
Future releases may include:
- ability to search / link / clone issues in another Project
- a mapping from field to field (similar to LNIO plugin)