When creating a issue in the storymap view I am trying to trigger a 'When Issue Created" automation rule that checks for condition if "sprint in (60923,65189)" (i.e if sprint is one of those sprints and then to edit issue fields label, component with values provided.
It works from the backlog view when I create a story in the specific sprint but not in the user story map view when i create in the sprint lane. For some reason Automation trigger is not recognizing the sprint when I create the story in the user story map view sprint horizontal lane. How to fix this? Is this a bug
My need: I have multiple teams and my need is to identify a specific teams board (or user story map view) and then to customize this rule to edit issue field "component" accordingly to match that team's value. Is there is a way to identify a teams/scrum board that an item is being created under in the automation section if not sprint?
Hi @Sreerampavankumar Govindarajula,
Are you using Easy Agile User Story Maps for Jira for your story mapping?
The issue here is that in User Story Maps we create the Issue in two stages: first we create the Issue, then we perform an update to set the Epic.
You may need to create a function that also runs on update, instead of (or as well as) on create. Another customer reported that they solved this by triggering the Automation for Jira rule when the Epic Link field gets changed.
Let me know if I can help out! Or feel free to reach out to us via support@easyagile.com
Stephanie Seymour | Easy Agile
For some reason it didnt take my original update why I posted second time below, deleting this one as it appeared to have refreshed after the fact. Pls read below update
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Yes I am using User story maps within Jira that shows in the header as Easy Agile. I tried looking for "On field value changed" trigger for "Epic Link" but it has Epic Name, Epic color etc but not link in the drop down. I tried Epic Name trigger to see if it will recognize the sprint but it didnt work. Also tried with "Issue Linked" trigger on "parent, child" and still it didn't recognize sprint. My companys Jira admin told me that they are planning to update our version end of this month and I will see if the newer version addresses this, we are currently at Jira v8.4.0
Only rule that works right now is when I use issue created trigger in combination with reporter field -listing individual team member names (as I know who is which team to identify and tag component value accordingly).
Background:
We have multiple team boards and each teams board is configured based on a filter that uses "Component" fld as a condition as we use the value in this fld to uniquely identify a team within the Jira project space. Hence the need here for me to identify the board/the user story map view for the team thats creating the story so I can tag/update the component field with the appropriate value for the story to not vanish from the story map view after its created. I need a way to uniquely identify the team board name when my rule triggers and unfortunately there is nothing like board id/name field in automation to use, hence I was relying on sprint id as it would be unique for each team so I could use that to determine which team and tag component accordingly (all this because story vanishes once created in the story map view currently as it doesnt have the component fld updated during creation from this view and the board is filtered on it)
See attachment if it helps
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Sreerampavankumar Govindarajula,
We're currently investigating an improvement to Easy Agile User Story Maps to ensure that when you create an issue, it meets the conditions to be displayed on the Story Map. This would mean you wouldn't need to use Automation for Jira to do this workaround. I've added your vote to this story so I'll reach out to you when it has been released - your Jira Administrator will then be able to update the add-on so you receive the update.
However, this feature requires a complicated trick to parse the JQL Filter of the Board. Could you help us with this development by sending an example of your Board Filters to us at support@easyagile.com?
Stephanie Seymour | Easy Agile
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Just want to update that with the latest version of Jira v8.11 that got updated this past weekend on our servers I noticed that the fix for user story map view is in i.e. the user story map view now automatically recognizes the board filter and applies it to the stories created so they don't vanish.
Also I figured the solution for my other issue for detecting sprint id when stories are created from user story map view. Instead of using "Create Trigger" if I use field value changed trigger on 'Sprint' field I am able to recognize/grab the sprint id for my checks. Just wanted to close the loop on this ticket incase it helps any in future with similar need. Thank you
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Sreerampavankumar Govindarajula,
I'm glad to hear your Jira (and Easy Agile User Story Maps app) have been updated to the latest versions and that the JQL-parsing feature released in Easy Agile User Story Maps 6.1.2 are working for you!
Thanks for updating us and sharing your solution to your Automation need.
Stephanie Seymour | Easy Agile
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi
I noticed this week as I am starting to plan for my PI event that this fix is not working in all boards.
This in reference to the fix you applied with the release Easy Agile User Story Maps 6.1.2. for “The board is pre-filling issues with components/labels when created on the Story Map to meet the board filter condition"
https://arijea.atlassian.net/servicedesk/customer/portal/2/RS-10990
I noticed that it works only if the board filter is simple enough
Ex:- project=NIP and component = xxxx . Cards created on user story map will NOT vanish. Jira automatically tags the component to the newly created cards -stories/bugs/task etc in the story map view
But if the filter is like below
Ex:- project=NIP AND (component = "User Enablement" OR component = Adroits) cards created on user story map will Vanish. Jira is still not tagging the component to the newly created cards in this case where the board query is having multiple components.
I used Jira automation to auto tag the component for now but wanted to let you know
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Sreerampavankumar Govindarajula -- Welcome to the Atlassian Community!
What do you mean when you say:
For some reason Automation trigger is not recognizing the sprint when I create the story in the user story map view sprint horizontal lane.
Is the rule triggering, but the sprint field is empty? Or, is the rule not triggering when the issue is created? Or, something else?
Best regards,
Bill
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Rule triggers but its not recognizing the sprint condition I gave. I tried using a add comment action with smart value {{sprint.id}} , {{sprint.name}} to validate and it was coming out blank which tells me its not recognizing the sprint where the story is being created in the user story map view
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks for that information.
I tried this from the backlog (creating a story in a future sprint), and it both triggered my rule and logged the sprint name. I do not have any story mapping add-ons to test what you are seeing.
I have experienced timing issues with the Create Issue trigger, whereby all of the data was not available yet in the rule processing. To mitigate that, I add a Re-fetch action immediately after the trigger before doing anything else.
If this is not a timing issue, there appears to be an impact from the story map and the setting of the field. If so, it appears you are already chatting with the vendor in this post.
__Bill
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks Bill. I tried using refetch as you suggested immediately after create issue trigger but still no luck. Its not identifying the sprint
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hmmm... This sounds like the sprint field is not populated in this path. If you are using an add-on for that story map, consider checking in with the vendor's support.
If not, hopefully someone else will see this question and comment.
Sorry I could not be of more help.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Correct. Not using an add-on. Its Easy Agile component part of Jira I believe.
Appreciate your inputs. Thank you very much
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
After reading the other comments in the other posts below, I can suggest one more thing to try, as this does appear to be an add-on and not a native part of JIRA...
The vendor's comment indicates that they add and then update issues. If the sprint field is set on the update rather than on the create, that is what you would need to trigger on: a Field Value Changed for Sprint.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Unfortunately "Sprint" is not an available field or option to choose in the automation trigger dropdowns (either for create/update)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Ah, I just noticed you are are on Server and not Cloud. Please take a look at your available triggers to find what you could use to detect an update. Then you may be able to use a condition to check for a change to the Sprint value using the changelog smart value.
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.