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

Excel export extended by releases #231

Merged
merged 7 commits into from
Sep 15, 2016
Merged

Excel export extended by releases #231

merged 7 commits into from
Sep 15, 2016

Conversation

heydenreich
Copy link
Contributor

@heydenreich heydenreich commented Sep 8, 2016

For projects and components: closes #223

  • possibility to extend excel export with (directly linked) releases
  • one line per project-release resp. component-release combination
  • (almost) complete export of project, component and releas
  • vendor, ClearingInfo, COTSDetails in separate columns
  • export respects filter (but not keyword search)
  • export button only enabled when filter parameters and view consistent

@maxhbr maxhbr self-assigned this Sep 8, 2016
if(type == SummaryType.DETAILED_EXPORT_SUMMARY){
setDetailedExportSummaryFields(document, copy);
} else {
copyField(document, copy, _Fields.ID);
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This could be moved to a verbosly named function

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is just a

listOfFields.stream()
    .forEach(renderedField -> copyField(document, copy, renderedField));

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Did the first one, but not the second.

try {
projects = projectClient.getProjectsById(ids, user);
} catch (TException e) {
log.error("Error fetching linked projects.", e);
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Same as above: this should fail hard

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ok

@heydenreich
Copy link
Contributor Author

Done with refactoring from my side. Is it enough?

@maxhbr
Copy link
Member

maxhbr commented Sep 13, 2016

Yes, code looks good.

* one line per project - linked release combination
* only directly linked releases
* more fields exported (almost all)
* vendor, ClearingInfo, COTSDetails in separate columns
* possibility to select whether linked releases are exported with the project
* names instead of couchDB ids for linked projects and linked releases
* excelExport for project respects filter
* selectable with or without releases
* respects filters (but not keyword search)
* more component fields exported
* prevents differences between excel export and view
* button is automatically enabled as soon as page is refreshed by "Apply Filters" or "enter" on an input
Copy link
Contributor

@mcjaeger mcjaeger left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

tested on vagrant based build and with projects import from mock and manually created releases to have multi release component. Also tested filtering with components and projects and both report types. All good.

@mcjaeger mcjaeger merged commit e80acda into master Sep 15, 2016
@heydenreich heydenreich deleted the dev/projectExcelExport branch October 25, 2016 11:59
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Table export of projects (the one the user can download) extensions
4 participants