On 30/09/13 21:51, Joe Dreimann wrote:
On 30 Sep 2013, at 16:25, Serge Bykov <[email protected]> wrote:
Yes, I deciphered that as being the intent, but maybe the default copying over of the
page would help with making this more new-user friendly. I felt that I had to at
least create default page before sharing the upgraded system with the team.
Especially since when selecting a different product from the Dashboard /
<products> drop down I am being redirected to the WikiStart page again,
instead of staying in the tickets dashboard and refreshing it for the tickets of the
selected product. I then have to click on the Tickets to get back to the tickets
view. Not sure what is the logic for being sent to the wiki page when I'm clearly in
the tickets view and just want to switch the product and see the tickets for the
selected product?
Cheers,
Serge
I wouldn't expect you to land on the Wiki Start page when you navigate to a
product, but on the dashboard-style Product page. That would seem more helpful
to me.
Yes, I think this would be better behaviour when navigating from a
ticket related view to a new product.
I think I have mentioned in another thread that I would like to see the
breadcrumb available throughout the system. Under that kind of setup I
would suggest that product switching should attempt to stay in the same
kind of page as was just left. At a minimum we could have:
* products/<src>/wik/path -> products/<dst>/wiki
* products/<src>/ticket_related_path -> products/<dst>/dashboard
It may be nice to take this further and allow any general
* products/<src>/<section>/path -> products/<dst>/<section>
There will be some values for <section> that will not have a matching
handler and so we may need to specify mappings and fall back to the
products/<dst> option for any that are not defined.
Cheers,
Gary
