I'm configuring JETI for a big JIRA instance. And I'm facing, that there is a big time wasting thing in configuring JETI, when setting up a Combination of Issue Type, Notification Type and email template.
1. Notification Scheme must be submitted for many projects of the same kind. Now and in the Future.
2. It should be simple and fast
Now my proposal is to have Context Schemes
I hope for you will consider this in future release!
If you leave Project empty in a Context, then the Context will apply to all projects.
Likewise, if you leave type empty, the Context will apply to all types.
This means that varying project and type, you can make Contexts cover one or all project(s) and one or all type(s).
is this issue: https://metainf.atlassian.net/browse/JETI-186
It will allow you to use JQL to to specify the scope of a Context. You'll be able to do something like
"project in (P1, P2, P3) AND type in (T1, T2) AND priority = Critical"
or do something more complex:
"((project in (P1, P2) AND type in (T1, T2)) OR (project in (P3, P4) AND type in (T3, T4, T5))) AND priority = Critical"
This means that using JQL you'll be able to define a Context and apply it multiple projects and/or types.
We have already released a version where you can add multiple event notificatios in a notificaiton template with different JQLs to better target your notifications.
Now this kind of targetting is coming to Contexts using JQL.
In the past, Portfolio for Jira required a high degree of detail–foresight that was unrealistic for many businesses to have–in order to produce a reliable long-term roadmap. We're tur...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs