Feature #10140

Allow certain fields in an issue to be designated as uncommon for display purposes

Added by Gerry Hawkins over 10 years ago. Updated over 9 years ago.

Status:ClosedStart date:
Priority:NormalDue date:
Assignee:-% Done:


Target version:-


There are certain fields, regular or custom, that while needed as part of an issue are not needed regularly, or are used infrequently.

It would be nice to be able to mark such fields as uncommon and allow those fields to be not displayed by default. This would help in keeping the UI clean and not cluttered. Much like the existing 'Change properties'. Except that these issues would typically be found in the lower part of the UI rather than just the top.

This sounds similar to #2618. Although a larger version of this would be to use the example of the workflow mechanism to select which fields would be in the uncommon area by issue type and role.

Related issues

Related to Redmine - Feature #12005: Mightful workflow field enhancement: hide New
Related to Redmine - Feature #12250: Configure order custom fields New
Duplicates Redmine - Feature #2618: Move some change properties fields into the "more" link New 2009-01-29


#1 Updated by Daniel Felix over 9 years ago

  • Category changed from Issues workflow to UI


this is a good idea. This setting would be helpful.
Maybe this settings could be set by workflow or in the projectconfiguration.

This is a problem which getting seriously on projects with many different custom fields, which must be writeable (which means i can't just hide them #8050) but they shouldn't be displayed all the time. In addition with #12250, this could be really helpful to get a cleaner interface!

#2 Updated by Daniel Felix over 9 years ago

I'm closing this in favor of #2618. This is a duplicate as described in the issue description. The idea with the workflow management could be good.

#3 Updated by Daniel Felix over 9 years ago

  • Status changed from New to Closed
  • Resolution set to Duplicate

Also available in: Atom PDF