Vote #79441
未完了Move issue attributes to their own section in issue page
0%
説明
I would like to move the issue attributes to their own section in issue page from the following reasons:
to implement a collapse/expand feature (#29034)¶
to make the issue page more structured and more easily to read/scan¶
to allow in the future more improvements, like a sticky issue bar¶
Before:
!{width:50%; border: 1px solid grey;}before.png!
After:
!{width:50%; border: 1px solid grey;}after.png!
journals
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
The patch must be applied after #29033.
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
What do you think about changing the section name from "Attributes" from "Fields"?
In Redmine, "Status", "Priority", "Assignee", and so on are called "Field" (e.g. "standard fields", "core fields", "custom fields", "fields permissions").
--------------------------------------------------------------------------------
I have updated the patch to change the section name from "Attributes" from "Fields". It is consistent with the terms already used in Redmine such as "standard fields", "custom fields", and "fields permission".
Marius, is that OK with you?
!{width: 764px; border: 1px solid #ccc;}fields-instead-of-attributes@2x.png!
--------------------------------------------------------------------------------
You're right, in the administration area all of them are fields (standard, custom), but in the issue page, the fields are displayed based on different criteria.
In a scenario with all types of custom fields, the issue page will have the following sections:
1. All standard fields excepting description + All custom fields excepting full-width custom fields
2. Description (standard field)
3. Files
4. Full width custom fields
5. Subtasks
6. Related issues
Besides 5 and 6, all of them are fields. At the same time, if we look in the edit issue mode, we will see that the label used there is "Change details" and not "Change fields" or "Change attributes". So, I don't know what to say about which label should we use.
Another concern is related to Jean-Philippe comment added to the collapsable sidebar (#21808#note-29) where he said " _I'd prefer not to add this to the core. I find it awkward to toggle some part of the UI._ " and the final scope of this change is to implement a toggle mechanism for issue sections (#29034).
Even if I'm the author of this ticket, with all of these in mind, I'm more in favour of getting more feedback on this (at least from Jean-Philippe) because without a toggle mechanism, this ticket is not a real improvement.
--------------------------------------------------------------------------------
I don't see the benefit of adding this section for now. It just eats up a bit more vertical space.
--------------------------------------------------------------------------------
related_issues
blocks,Closed,29033,Move attachments to their own section in issue page
blocks,New,29034,Option to collapse/expand issue sections