Why do my contributors not see the full timeline view (including grouping)

[André]

Hello,

I was looking around, but couldn't find the answer to my question. We have set up JPD for a roadmap view for our IT department. I've added all users in Jira as contributor because we want the whole organisation to be able to pitch in with ideas and see the current roadmap.

For the roadmap we use a timeline view which we group on teams. So every teams has their own swimlane, which makes it nicely clustered for viewing by our colleagues.

Today I discovered that the creators see the proper timeline view we tailored to our needs, but our colleagues just see a full list of all ideas, no grouping at all, which just makes it 84 ideas underneath each other. I've giving the specific colleague who showed me what he saw to creator and now he does see the proper view. So apparently it's tied into rights?

How can I make the timeline view, including grouping available to all contributors as well?

Thanks in advance for any help you can give me on this.

Kind regards,

André van der Zijden

[Tanguy Crusson · Accepted solution]

Hi @André it looks like we have a bug there - but even after we fix it, you'll still need to do something so your contributors can get the info they need from that view. 

Context: to be able to see the "Teams" object (Atlassian platform object) someone needs to be a paid user of Jira on the site. It's not available to non-licensed users, e.g. contributors. 

On top of that you found a bug we were not aware of and are going to fix: in cases like this the timeline is meant to show the groups and show "you don't have access to view this object" in lieu of the team names. 

In your case, if you want to show team names and ideas grouped by those, you'll have to create a select field with the team names unfortunately (vs using the Team field). Or give everyone a Jira license (but that would be more costly). 

[André]

Hey Tanguy,

Thanks for your response. Ok so the Jira teams are for Jira users, check. I'll convert it to a field and see if that works. It's not a problem for us, we decided to use the teams as we saw them already available, but a custom field will work just as well I guess.

Thanks for your fast response!

[André]

A field works, which is actually better for us. So thanks for the help and insight into the workings of the system.

[Tanguy Crusson]

Thanks for getting back to me, and glad it worked!