In typical Agile fashion, every few weeks we try to make the tasks for JIRA admins slightly easier. During this sprint our main focus was to minimise the tedious work by allowing you to create multiple issues with one operation. Exocet 2.12 also allows you to direct projects only to the relevant teams and have more control over your post function configurations.
Dynamically create multiple issues with one operation
If you are new to Exocet, our handy add-on’s operations are a great way to create linked issues, as the source issues are injected directly into the target fields. This is a great way to provide structured and well-established workflows by automating the repeating (and boring) tasks.
Yet when business requirements demand that dozens of issues are created at the same time, the configuration of Exocet can take a long time. You might have experienced frustration when you receive an update on a certain business need, and you just know the rest your day is going to be focused on adjusting the configuration.
At Valiantys we despise boring tasks – which is what made us create Exocet in the first place! With this new version of Exocet, you can now create several issues with one operation.
Let’s take the example of a software team using JIRA. When the team starts working on a new sprint, team members review all the user stories and create the respective sub-tasks.
They include relevant information coming from the main issue into subtasks, like affect version, attachments, etc.
This boring task can now be performed in a few clicks:
In this example, when the Define sub-tasks post function is executed, a transition screen is displayed. From this screen, users can select the sub tasks to create from a predefined list (the Tasks to perform field) but they can also define additional tasks not listed above with the Additional tasks field. When the transition is executed, Exocet will create sub-tasks for each item selected.
Only propose relevant projects when executing an operation
JIRA is the perfect tool to facilitate team work. It has become so popular that it exceeded its original goal – to help software development teams. Now it is used by HR, marketing, sales, and many other teams.
However the consequence is that a large number of projects are now on the same instance. A good way to keep them organised is to group them by category.
When configuring an Exocet operation, admins have the option to let the user select the target project. This is handy when the same operation applies to many projects (ie: create a bug from a user request raised on a support portal). In this case, this flexibility comes with a price as selecting the project in a JIRA instance with too many projects can hinder productivity. Studies have actually shown that an excess of choices often leads us to be less, not more, satisfied once we actually decide.
In this new release, we added an option to Exocet operations: instead of selecting a JIRA project as target of an operation, you now have the option to select a category. This means that your software development operations can be configured to only display projects belonging to the related category.
Easier post function configuration
Exocet operations can be either executed manually from the issue view or from a post function. Some use cases – like employee on boarding – can lead to creating dozens of post functions (one per operation).
To reduce the pain of configuring your workflow, with this version you can now execute many operations from the same post function.
An easier configuration equals happier JIRA admins!
Try Exocet for JIRA today
