-
Notifications
You must be signed in to change notification settings - Fork 20
Linked releases - clearing status is also important #177
Comments
There are currently two possible views where linked releases are displayed:
|
(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... |
(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 |
@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:
--> Shall I stick to the plain treetable? |
@mcjaeger @alex-evo Paging and treetables has also some special effects ;-) |
OK, understood, as we discussed, let's keep to display the information then. |
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.
The text was updated successfully, but these errors were encountered: