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

Table export of projects (the one the user can download) extensions #223

Closed
mcjaeger opened this issue Aug 31, 2016 · 3 comments · Fixed by #231
Closed

Table export of projects (the one the user can download) extensions #223

mcjaeger opened this issue Aug 31, 2016 · 3 comments · Fixed by #231
Assignees
Milestone

Comments

@mcjaeger
Copy link
Contributor

mcjaeger commented Aug 31, 2016

In the project main listing view, the user can get an export of projects as a table document (for use with libre office for example) . Following enhancements are proposed:

  • The export should reflect the actual selection / filtering in the project view.
  • The export should also contain a possibility to list the linked releases with release information.

For the second point, the desired output is denormalized: this means roughly the following structure

| project1 | project attributes ... | release1 linked to project1 (with component name) | release attributes ... |
| project1 | project attributes ... | release2 linked to project1 (with component name) | release attributes ... |
| project1 | project attributes ... | release3 linked to project1 (with component name) | release attributes ... |
| project2 | project attributes ... | release1 linked to project1 (with component name) | release attributes ... |
@mcjaeger mcjaeger added this to the 1.5 milestone Aug 31, 2016
@heydenreich heydenreich self-assigned this Sep 1, 2016
@heydenreich
Copy link
Contributor

heydenreich commented Sep 1, 2016

A requirement is that the export respects the current filter.

This is only partly implemented with components and projects (!) already: the "keyword search"-JS-filter is respected, the other filters are not.

@heydenreich
Copy link
Contributor

Which linked releases should be listed: only the releases directly linked to the project?

@mcjaeger
Copy link
Contributor Author

mcjaeger commented Sep 2, 2016

yes. otherwise it would be redundant, because then, the linked sub projects will be likely listed too as separate entry.

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.

2 participants