It's all about the answers!

Ask a question

Exporting in RRC


Don Hoeksema (26167) | asked Jun 22 '12, 12:33 p.m.

Does anyone know what we are doing wrong when we are exporting RRC information into Excel? We created a filter to get the fields we need. But when we export a 2nd set of information, the export is retaining the information from the 1st export. The only way we can make it work is to create the filter each time we do an export. What are we doing wrong?



Comments
Benjamin Silverman commented Jun 24 '12, 1:21 p.m. | edited Jun 25 '12, 8:34 a.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER

Hi Don,

Can you please state which version you are using as well as more detailed steps to reproduce the problem you are having?  It sounds like a potential defect but would like to have some more information.  Thanks,

One answer



permanent link
Don Hoeksema (26167) | answered Jun 25 '12, 9:24 a.m.

We are currently usinf version 3.0.1.1

Here are the steps to recreate what is happening:

    Create collections in the appropriate project(s).

    Create a filter with the columns specific to what we need to export (this filter is created within a collection)

    Save the filter in the Saved Filters section

    The saved filter is available now for all collections

    Go into a collection and from the Saved Filter select Export

    This will export the requirements into a CSV file

    The problem is that the export will only work for the first collection, it will not work on additional collections, the only way to make this work is create the filter for each collection.

This may be design, since we are creating a filter within a collection and expecting it to work when we jump into another collection.  It is just a horrible time waste to create the filter for each collection.  Any insight into why this is working this way or an alternative solution would be greatly appreciated.


Your answer


Register or to post your answer.


Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.