Skip to content
This repository has been archived by the owner on Jul 25, 2018. It is now read-only.

Linked releases - clearing status is also important #177

Closed
mcjaeger opened this issue May 20, 2016 · 7 comments · Fixed by #253
Closed

Linked releases - clearing status is also important #177

mcjaeger opened this issue May 20, 2016 · 7 comments · Fixed by #253

Comments

@mcjaeger
Copy link
Contributor

mcjaeger commented May 20, 2016

For linked releases the clearing status is also important to see.

Situation: some creates a component with release. Then the release has linked releases. The clearing status of these linked releases should be visible to in the linked releases view (one of the menu items on the left side of the releases detail view).

Then, the maintainer of a component/release has an overview about the involved sub releases.

@mcjaeger mcjaeger added this to the 1.4 milestone May 20, 2016
@mcjaeger mcjaeger modified the milestones: 1.5, 1.4 Jun 17, 2016
@maxhbr
Copy link
Member

maxhbr commented Aug 31, 2016

There are currently two possible views where linked releases are displayed:

  • Linked Releases And Projects (is also the clearing status of the linked projects important?)
  • Linked Releases Hierachy (might be mergeable with the tab Clearing Status)

@mcjaeger
Copy link
Contributor Author

(requires discussion): actually, does it make sense that clearing status is OK but for sub releases not? also adding sub releases poses questions here to clearing status of release...

@mcjaeger
Copy link
Contributor Author

(from discussion): 1) actually it is about the releases-subreleases page, not the linked releases of a project or other project portlet views. There is a simple table (which could be update to jquey tables as in other views) where the clearing status would be helpful. 2) displayed field would be field 17: clearingState

@heydenreich
Copy link
Contributor

@mcjaeger @alex-evo : Did you realize that the table in question is a treetable. You can combine treetable with DataTable - I just tried it, but the result is probably not what you want:

  1. The search of the DataTable finds only sub-releases if they are actually visible, i.e. if all ancestor-releases are expanded. If you start with a table, where nothing is expanded, the search will not find a sub-release.
  2. The sorting of the DataTable mixes all visible releases, i.e. the child releases are not displayed under the correct parent release any more.
  3. If search and sorting are not useful - why use datatable at all?

--> Shall I stick to the plain treetable?

@heydenreich
Copy link
Contributor

heydenreich commented Sep 29, 2016

This is how the combination treetable datatable looks like if you sort (child -releases are subreleases of parent, not of some other release.)
image
(In this case it is sorted according to name which is special anyway, but if you sort according to any other column, this can happen as well.)

@heydenreich
Copy link
Contributor

@mcjaeger @alex-evo Paging and treetables has also some special effects ;-)

@mcjaeger
Copy link
Contributor Author

OK, understood, as we discussed, let's keep to display the information then.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants