[#JRA-10663] Custom field in incorrect order in full content view

JIRA

Custom field in incorrect order in full content view

Created: 23/Jul/06 11:27 PM Updated: 02/Nov/06 09:02 PM

Component/s:

Custom Fields, Issue navigator

Affects Version/s:

3.6

Fix Version/s:

3.7

Time Tracking:

Not Specified

Issue Links:

Reference

This issue relates to:

~~JRA-10404~~ Make 'views' of content (single issue and search request) pluggable, and rewrite default implementations in velocity

~~JRA-9213~~ Word export shows custom fields at bottom of document

Participants:	Mei Yan Chan [Atlassian], Neal Applebaum, Nicolas Bell and Scott Farquhar [Atlassian]
Since last comment:	91 weeks, 4 days ago
Resolution Date:	22/Oct/06 09:28 PM
Labels:

Description

« Hide

The custom fields are not ordered as configured in full content view. Users need to have it configured in the same order as seen in their screen while viewing full content via HTML or Word.

All

Comments

Work Log

Change History

Sort Order:

Ascending order - Click to sort in descending order

[ Permlink | « Hide ]

Neal Applebaum - 24/Jul/06 09:46 AM

The custom fields should appear at the top, as on screen, and fixed in the linked issue. I assume this bug is that the full content view is inconsistent.

[ Permlink | « Hide ]

Nicolas Bell - 27/Jul/06 10:32 AM

Neal,

I reported this bug to support. You are correct to assume that his bug relates to inconsistent order of custom fields when viewed as full content. I can provide further info as well as examples if needed.

[ Permlink | « Hide ]

Scott Farquhar [Atlassian] - 28/Aug/06 06:59 AM

We need to verify that this is still an issue in JIRA 3.7, as ~~JRA-9213~~ seems to suggest it has been resolved in JIRA 3.6.

[ Permlink | « Hide ]

Nicolas Bell - 28/Aug/06 09:35 AM

This issue does exist in JIRA 3.6.2.

[ Permlink | « Hide ]

Scott Farquhar [Atlassian] - 22/Oct/06 09:28 PM

In JIRA 3.7, custom fields are rendered in the same order as on screen.