Remove the affectedVersion/fixVersion fields and redesign the Issue Navigator sidebar?

[Philipp Oelwein]

Within a specific project setup we would like to replace the affected/fixedVersion fields with a single "Version" field. The project doesn't require the concept of an error in version X fixed in Version Y.

"Version" in this context refers to language versions. No need für numeric versions.

Well, it's no problem to set up a user defined field (e.g. selectbox) and fill it with preset content. Searchable, sortable, filterable ... fine. Also no problem to make a screen with no fV and aV on it and "language version" instead. Put it all in field schemes, screen schemes and so on, fine.

BUT: The main disadvantage will be that in the issue navigator in the left column there will be the filter selectors für affected and fixed version on top very prominently and the newly defined "language version" will be several screen pages to scroll downwards. The average user will stick to the former version selectors and mix everything up. We want to avoid this.

Is it possible to define a issue navigator view without the Jira-own affectedVersion and fixVersion fields (field scheme allows only user defined fields to in- or exclude)? Or at least some kind of rearrangement of the filter column of the issue navigator so the aV and fV can be moved down as far as possible and the to-be-used language version up as far as possible?

Any other hints or ideas?

Thanks in advance
Philipp

[Philipp Oelwein · Accepted solution]

Conclusion:

• No fiddling with internal fields and their presence and order in the filter column
• Would require work on velocity templates
• Any simpler solution is just workaround

Cheers
Philipp

[Raquel Moracho Sánchez]

can anybody tell me what are the classes to modify the issue navigator screen? (velocity template, action that renders the results, etc.)

Thank you

[Philipp Oelwein]

Hmmmmm,

does that remove the affected Version and fix Version fields from the issue navigator search property column?

Regards
Philipp

[Karie Kelly]

You can create a field configuration that hides the affected version and fixed version.

Created a field configuration scheme that has the newly created field configuration

Assign that field configuration scheme to your project that you don't want to use these fields.

[Philipp Oelwein]

Hmmmmm,

does that remove the affected Version and fix Version fields from the issue navigator search property column?

Regards
Philipp

[K Kelly]

No since the Issue Navigator is not project specific in terms of a column to select to view. However, if you select the project in the left sidebar and then click on the link that appears below the project selection to update the fields, those fields will not appear in that section for a user to utilize.

[Matt Bates]

There is no way to modify the Issue Navigator without hacking the velocity templates. I would recommend reusing either fix or affects version for this purpose (or even component).

You'll find there is quite a bit of magic handling of built in fields still in Jira, and its often easier to roll with somethign that doesn't look quite right but is easy to use, than trying to get it perfect.

[Philipp Oelwein]

I would recommend reusing either fix or affects version for this purpose (or even component).

That's what we do currently and want to simplify (component is used otherwise).

The problem with this is that the average user takes only one of the two version selectors into account when reporting, the other average user takes only the other one of the two version selectors when searching or using filters. And so filter results are incomplete.

The version fields can't be set to "required" for other reasons (the issue type is used in many different contexts). Seems the only solution is a different issue type with these fields set to required. Ah well.

tnx anyway
Philipp