Project

General

Profile

Actions

Patch #4277

open

Add "hide prefixed projectname from issuesubject on issuelist" setting

Added by Mischa The Evil about 15 years ago. Updated about 14 years ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
Administration
Target version:
-
Start date:
2009-11-24
Due date:
% Done:

0%

Estimated time:

Description

This issue is extracted from #3100 and it's relatives. The patch adds a new system-wide, issue-tracking setting (hide_prefixed_projectname_from_issuesubject_on_issuelist) which provides the administrator an option to hide the subproject name (which is prefixed in front of the issue descriptions on mainproject issue lists) completely.
Such a setting can be useful if the site is configured to display the project-column be default.

The default setting is equal to as it is currently(the projectnames are shown prefixed to the descriptions).


Files


Related issues

Related to Redmine - Feature #2889: Separate project field and subject in cross-project issue viewClosed2009-03-03

Actions
Follows Redmine - Feature #3100: Better display of subprojects activiry and tickets.Closed2009-04-02

Actions
Actions #2

Updated by Jean-Philippe Lang about 15 years ago

What about fully removing the project name from the issue subject ? since the project can now be added as column.

Actions #3

Updated by Mischa The Evil about 15 years ago

Jean-Philippe Lang wrote:

What about fully removing the project name from the issue subject ? since the project can now be added as column.

Good idea. I see you've removed the project name prefixed to the issue subject already in r3112.

Maybe it's best to also enable the project column as a default issue-list column in the default configuration (source:/trunk/config/settings.yml#L127)?

Actions #4

Updated by Mischa The Evil about 15 years ago

  • Status changed from New to Resolved

This patch can be closed without further changes as being obsoleted by changes in the core, when the project column is displayed on issue-lists by default IMHO.

Actions #5

Updated by Mischa The Evil almost 15 years ago

Mischa The Evil wrote:

Jean-Philippe Lang wrote:

What about fully removing the project name from the issue subject ? since the project can now be added as column.

Good idea. I see you've removed the project name prefixed to the issue subject already in r3112.

Maybe it's best to also enable the project column as a default issue-list column in the default configuration (source:/trunk/config/settings.yml#L127)?

Mischa The Evil wrote:

This patch can be closed without further changes as being obsoleted by changes in the core, when the project column is displayed on issue-lists by default IMHO.

Jean-Philippe, What do you think of this? Now that the project name prefixes on issue-subjects on the issue-list are removed ánd without the project-column not actived by default on issue-lists, the situation can occur that a user interprets the issue-list as being for the current project only.
In my opinion such should be avoided if possible... ;)

Actions #6

Updated by Mischa The Evil about 14 years ago

  • Status changed from Resolved to New

Mischa The Evil wrote:

Jean-Philippe, What do you think of this? Now that the project name prefixes on issue-subjects on the issue-list are removed ánd without the project-column not actived by default on issue-lists, the situation can occur that a user interprets the issue-list as being for the current project only.

I need to make my statement clearly more obvious. Here it comes: "Now that the projectname-prefixes on issue-subjects on all the issue-lists are removed ánd without the project-column not actived by default on project issue-lists ánd with the setting ' Display subprojects issues on main projects by default ' set to TRUE, the situation can occur that a user interprets the project issue-list as being for the current project only while it also includes issues of the projects' sub-projects (and their sub-projects, I guess...)"

For the above I'd suggest to enable the project column as a default issue-list column in the default configuration (source:/trunk/config/settings.yml#L127).

Note: The patch could be considered obsolete.

Actions

Also available in: Atom PDF