Hi all,
we are creating an automation based on a few lookup issues and lookup tables to get a list of Jiras that were created or closed during the last sprint on each sprint completion into an email.
We unsuccessfully tried to get the sprint name and dates into the email as well, with the smart values below:
{{issue.sprint}}
{{sprint.endDate.jiraDate}}
{{sprint.endDate.last.jiraDate}}
We also tried to use those smart values in a lookup table and the best we could get was a list of issue keys. Considering that we used the "sprint completion" trigger, is there a way to get those sprint details in the email?
Thanks!
Hi @Urmas Kungla!
Let's split the JQL according to the conditions:
1. Not Epics:
issuetype != Epic
2. Not linked to any Epic
"Epic Link" is EMPTY
3. Not subtasks of any Epic:
... AND parent not in (<ID1>, <ID2> ...)
Where ID1, ID2 are ids of Epics.
4. Not subtasks of parent tasks that are linked to an Epic
This last condition is already covered by the 2nd one. Subtasks have the same Epik Link as their parents.
So, the final JQL will look like:
issuetype != Epic AND "Epic Link" is EMPTY AND parent not in (<ID1, <ID2>, ...)
Hi
Thank you for your suggestions.
Regarding this part:
parent not in (<ID1, <ID2>, …)
This solution unfortunately is not suitable because there will be many different Epics which I can't control and therefor the script should be dynamical- it should be able to filter by issue type "Epic" not by single ID (or multiple ID-s).
Any ideas?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi!
Yes, there's a workaround.
You should link all the epics to an issue (<ISSUE>) and tell everyone they need to link all their new epics to this issue.
After that you can use:
parent not in linkedIssues(<ISSUE>)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Yeah, I thought about that too but this will not work for me- it's an extra move that EVERYONE has to REMEMBER all the time. It'll never work out.
Any other ideas? Or is it really a feature request?
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.