Hi,
I would you go about sending a list of issues per assignee and per week across all projects in JIRA/JSM.
I'm having a hard time figuring that one out without creating issue filters but that would defeat the purpose of the automation if I have to create a filter for every new user though.
Any help is appreciated.
Thanks!
Cheers.
Julien.
Just wanted to update this question with an up to date solution. There's now a way to achieve this through automation. See https://support.atlassian.com/automation/kb/automation-rule-to-send-single-email-for-all-issues-per-assignee-due-next/ for details.
Hi @Julien Béchade
If you are interested in receiving a weekly email per assignee with time in status or time to assignee data, you may find this article helpful: https://community.atlassian.com/t5/App-Central-discussions/Time-in-Status-email-notification/m-p/2567085#M3088
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I do think an Issue Filter with a Subscription would be easiest.
You can create a dynamic filter, that provides the results based on the user who is logged in, so you'll only need one filter - not one filter per user. This uses a function called currentUser().
---
To do this...
assignee = currentUser() and statusCategory != Done
---
Users should then receive an email per day with their assigned issues from this one filter.
Whilst you can do this via Automation, this is the native feature for this.
---
Just to note - you can also provide this view within Jira itself, either...
---
Let us know what you think :)
Ste
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Ste Wright and thanks for your help!
I did not think about subscription at all and I'll explore that solution further, thanks!
However, I need to be able to customize the email, order the different tasks per project and status, etc. and that does not seem to be possible with subscription. My Google research led me to that issue from the automation team so it seems to be in the pipeline to be able to work further on the `lookupIssues` object.
Again, thanks for your help!
Cheers.
Julien.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You can order the Tasks per Project, per Status by using the ORDER BY function in JQL - but they'd still be in just one list.
For example...
assignee = currentUser() ORDER BY project ASC, statusCategory ASC
...would provide the results ordered by Project (in alphabetical order), then by Status Category (To Do Statuses, In Progress Statuses, Done Statuses).
---
If you're going to use Automation so you can customise the body of the email - it could be quite complex.
Some of it is relatively simple - for example - you can use a Scheduled Trigger to send the email once a week. But you would need:
This would need some research and quite a bit of testing to get right, I think.
---
I do think though if you're going to create custom views based on Projects, Statuses, etc - it'd be far easier/better to use Dashboards.
It will make creating filtered lists and displaying them easier, it will be real-time, and there are multiple gadgets which could help summarise information for users - for example...
You can see a summary of what gadgets are available in Jira Software on this help page.
Note: You could still send an email using Automation each week - and just link to this Dashboard each time!
---
Another alternative might be to have a Confluence Page, and using the Jira Issues Macro, and the Jira Charts Macro, to segment your data.
Ste
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Ste Wright ,
The requirements for the weekly digest is email because the public is new to JIRA/JSM and is primarily using email so dashboard wouldn't be an optimal solution.
But subscription looks like a good candidate before the CodeBarrel team implement a meaningful way to work further on the `lookupIssues` data. I realized that it would be overly complicated to use automation at the moment to achieve my goal.
Thanks for your help!
Cheers.
Julien.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.