A user with only Browse Project permission can't see the story map. The user gets a We cannot find your Epic Issue Type error.
If I grant the Create Issues permission to the user, he can see the story map.
Is this an intended behavior?
Hi Bernhard, thanks for reaching out.
This sounds like the individual user may not have permission to access/view all the filters referenced within your board filter query. For example, the query for the board may look like "Filter in (ABC, DEF) ORDER BY Rank" but the user may not have access to project/board ABC, leading us to throw the error.
Users should be able to view the story map, but not make any changes, as long as they have Browse Project permissions for all projects included by the board filter.
If you would like some help troubleshooting the JQL please send your board filters to us at support@easyagile.com and we would be more than happy to find a solution that works for you.
Kind Regards,
Seamus Kieran
Easy Agile Support Team
Hi Seamus
Thanks for your reply.
The boards settings are as follows:
Shares: Shared with everyone with permission to browse the 'XXX' project
Filter Query: project = XXX ORDER BY Rank ASC
The user can apply this filter elsewhere, can see the backlog but whenever he clicks the User Story Map button he gets the error.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Bernhard,
This is really quite strange, can you please gather and send the troubleshooting information to support@easyagile.com so that I can investigate further?
Thanks,
Seamus Kieran
Easy Agile Support Team
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
We have same issue with ne colleagues.
Any update/solution?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @bk
We currently still require the Create Issue permission to load the story map, however we are aware that this is suboptimal. We built it this way as we believe that the vast majority of agile teams around the allow all of their team members to create issues.
We can see the Create Issue permission requirement being removed in future, however we have no immediate plans to work on this.
Sorry I cannot be of more assistance at this time.
Regards,
Dave Elkan
Co-CEO, Easy Agile
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.