Gemini Community Support Site

This Gemini community support site can be used to find solutions to product issues. You can log in using Open Id, Google Profile and even Facebook. Feel free to ask a question or browse FAQs and documentation. Product tour videos are also available along with how-to videos demonstrating key Gemini capabilities.




Link in component's tree

web-app

I have projects with a lot of components with 3 or 4 levels of hierarchy and in that projects the users usually navigation in the tab of components.

In previous version (3.5.3) the users usually open that tab component of the project (http://.../project/Project.aspx?Tab=Components&PROJID=x), find the component in the tree of components and clicked in the component to show (and work in) the issues of that component.

In version 3.6 the component's tree haven't links, we only have links in the chart or the list but isn't the same thing because we have a lot of components and it's hard to find them in list. It's more easy in tree.

Any chance to have links back to component's tree?

jsaraiva
· 1
jsaraiva
Replies (10)
helpful
0
not helpful

We are thinking about changing this. At the moment a click on a parent will collapse / expand. The change will be that the click navigates to the issues page and if you'd like to collapse / expand you will have to click on the [+] /[-] icons.

Your thoughts are welcome.


Saar Cohen
· 5000
Saar Cohen
helpful
0
not helpful

I think that is the best option.

This will be released in 3.6.1?


jsaraiva
· 1
jsaraiva
helpful
0
not helpful

Yes.


Saar Cohen
· 5000
Saar Cohen
helpful
0
not helpful

Hi.

It would also be nice if the list of components in the Project Summary had been nested


DOA
· 1
DOA
helpful
0
not helpful

Unfortunately, this will create problems with displaying as you can have unlimited nesting so it won't render nicely there.


Mark Wing
· 9108
Mark Wing
helpful
0
not helpful

That would be great, I understand displaying problems, but it could be a configuration in each project.

We could change the configuration project by project, and if in one project it won't render nicely, we turn off for that project.


jsaraiva
· 1
jsaraiva
helpful
0
not helpful

I have another issue with this tree that worked in 3.5.3 and doesn't in 3.6.1

If we click in the tree, we will see the issues of that component. So far is OK, but if after that we click in create issue, in 3.5.3 the previous selected component would be selected by default in the new issue.

In 3.6.1, the compoment isn't selected by default.

It will be great if this funcionality could be back to the application.


jsaraiva
· 1
jsaraiva
helpful
0
not helpful

Did you set default component for the project?


Saar Cohen
· 5000
Saar Cohen
helpful
0
not helpful

No, I haven't.

Because I don't want the same default component for all new issues.

I would like to have the component that has been selected in tree. And only in this case, if the user doesn't select a component in tree or list, the new issue shouldn's have a default value for component.

Like was in 3.5.3


jsaraiva
· 1
jsaraiva
helpful
0
not helpful

Mark Wing
· 9108
Mark Wing