|
History
| Log In
|
|
|
|
[
Permlink
| « Hide
]
John Sun - 13/Nov/03 09:14 AM
I agree with Chris, this would be a very helpful feature to have if your development effort includes different roles.
Dashboards should also be linked to permissions so you can set who can view them and who can edit them.
We have almost 800 users and this feature would be really useful.
Most of users have similar functions. Do you have any idea when it´s gonna be implemented? Thiago,
Unfortuantely I do not have an implementation date for this feature at the moment. Please, keep voting for this issue to show us that it is important to you. Thanks, The first question almost everyone asked when I first showed them the Jira dashboards was how they could just copy mine, or if they could copy from a template dashboard that I created.
For the developers who tend to like to customize and tinker to get their dashboard just "perfect" there is at least one business person who just wants it to work and be done. This would be a great feature. please allow simple sharing of dashboards soon. setting up a new team with multiple cross-project responsiblities is a royal pain in the neck.
In the spirit of agile development, permissions on sharing of dashboards, etc. can come later. The basics first, please! This feature would greatly be appreciated in our company as well. We have several projects that would like to design their own dashboards to share with the world.
Can't it work just like filters? Make it so I can share my dashboard pages? I doesn't even have to be complete dashboards, just pages. Please... This would be so helpful for large deployments.
I can't agree more, for large dev teams where it is all about the stats, a shared dashboard or dashboard page would be great.
This would be nice to see - shared portal pages would also be good (not sure if only the first page in the list is the dashboard or not).
Being able to create special pages for particular contexts and sharing them with a group would give Jira a big jump in terms of its management abilities. I'm just feeling this point now...
It would be great it you could share out dashboard pages or configure the default dashboard to use multiple pages and permission them by group. Hi all,
in our team we are working in distributed environment and this will be realy useful to share it among different sites. Vlasta Even in our small team this would be really useful. I've set up a fairly complicated dashboard, and would like to be able to share it with the rest of the team so they don't have to duplicate it. Please add this soon!
We also need the ability to set up multiple default dashboards to choose from. We will soon be over 400 users. Please make this available as soon as possible.
This feature is urgently required by my team. We need external customers to have one dashboard (so that they can report issues and see the issues they have reported) and also NOT be able to change it (otherwise they will break it and... need to call support to get it fixed!) - then the support team themselves need another dashboard (to allow them to see new unassigned issues and all the issues assigned to them) - Developers could also benefit from having their own dash with some standard developer filters.
Also - when new customers or staff members come along, we need to be able to roll out a standard dash to them that we can train them on. We don't want to have to configure it by hand each time. At the moment, our default dash has to be the dumbed-down customer-facing one, and all our internal staff need to configure their own additions to this. I agree to the above. My company is using Jira in distributed environment spread around the world in many timezones in the need for very different views and portals.
Hope you can please get this issue assigned and worked on. This is probably one of the most confusing things about JIRA – that I can't make views to share other than filters themselves. What is the status on this?
Thanks! This feature should bring much more effectivity to our work. It would be great for the users to share pre-defined statistics, charts etc.
Thanks in advance! adding the twohundredth vote on this issue.
One more vote for this - I was just looking at creating release centric dashboards with portlets focussed on a particular project/release and it would be great to simply share these with the other developers involved.
To those who have the chance to work with Confluence as well, there is a workaround while wating for this issue resolution : create wiki pages embedding jira portlets !
It's simple to do while requesting some discipline to make it deployable accross an organisation: that's it ! It's not as performant as a pure Jira approach, but it's barely enough to cover the essential needs. I hope this helps. Just duplicating many of the above request. We have business users that we need to set up. I'd like to:
1. Create the user Thanks Let me add my notes in support of this, from a chat with support...
I look forward to using such a feature in the future... I would definately like to see this feature implemented. It would make setting up new users soooooooo much easier!
Hi... it's been a while since a comment from Atlassian... is there any update on this? I'm curious whether there's even a forecasted release # for this feature and if not, what other features/cleanup you need to develop to lay the groundwork for this, since it is your 4th most popular feature and I understand we're still a ways off from getting the #1 feature of field-level security permissions.
Looking forward to learning more about when we'd be able to: Thanks! Personally, I got tired of configurig dashboards---and waiting for this feature. Check out JIRA Client by almworks. I have no need for this feature anymore.
Thanks, Hi,
Guys, unfortunately I do not have an implementation date for this feature. The reason is that there are a lot of popular feature requests, and we are trying our best to work through them. I am sorry for not being able to be more specific on time lines. Cheers, Hi Anton,
You say that there are a lot of popular feature requests, but this is curently the 4th most popular feature request so those of us that are following this issue are wondering what else exactly is taking precendence and why the voting seems to be being ignored? Thanks, Leon. Hi Leon,
The votes are not being ignored. In JIRA 3.9 we have implemented conversion of issues to subtasks - In JIRA 3.10 we are implementing Please note that when features are implemented, they stop being voted on, so the oldest issues always move towards the top. Another thing to keep in mind is that while voting is important it is not the only contributing factor to the features we choose to implement next. For more information about how we choose to implement new features please see: Having said all of the above, I would like to thank you for your feedback. Giving us information which shows which issues are important for you and why, does help us. Cheers, | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
New Feature
Open
Major
Save, reuse and share Dashboards (like dashboard picklist)
