Issue Navigator should show Default columns if Filter JQL is changed

Summary

In the Issue Navigator: List View, a user can designate a set of columns under My Defaults, which are the columns displayed for standard searches. The user can also designate a set of columns under Filter, which are specific to each saved Filter.

When a user initially runs a filter search, they can select to use the Filter columns to see specific columns for that particular filter. However, if this user changes the JQL and runs it, the current view will still show the Filter specific columns, instead of showing the My Defaults columns instead.

Whether this is by design or not is uncertain. However, this will directly conflict with the implementation of Exporting to Excel (Current fields), which should ... create a spreadsheet column for the issue fields that are currently displayed in your Issue Navigator.

What will actually happen is that the export will contain the columns under My Defaults, even though what is onscreen will be from the columns under Filter.

Environment

Reproduced up to JIRA 7.0.9

Steps to Reproduce

1. When viewing list of issues from a specific filter (e.g. ExampleFilter), add a new column value. This value:

• Should not be present in the My Defaults option.
• Needs to be added to the Filter option.

2. Modify the JQL, and then run it, so that we are looking at a different result set (but are now editing ExampleFilter)

3. Export as CSV (Current Fields)

Expected Results

The export should contain all fields in the current view, which is still the Filter view.

Actual Results

The export will include all columns from the My Defaults option, rather than what is onscreen at the time.

Notes

This properly explains the behavior described in JRA-36991 : Export to Excel (Current Fields) not using the fields on screen if a filter has been edited, which did not have clear repro steps and was confused with JRA-34812 : Export to excel (current fields) does not show all columns present in the issue navigator, which did not address the issue.

Workaround

Either:

• Save every JQL modification as a new or existing filter, and ensure that the column(s) being added are added to the Filter set
• Add the column(s) to the My Defaults set prior to exporting.