Patch #4277

Add "hide prefixed projectname from issuesubject on issuelist" setting

Added by Mischa The Evil almost 8 years ago. Updated almost 7 years ago.

Status:NewStart date:2009-11-24
Priority:NormalDue date:
Assignee:-% Done:

0%

Category:Administration
Target version:-

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).

add-setting-hide_prefixed_projectname_from_issuesubject_on_issuelist-r3078.patch Magnifier - against trunk@r3078 (2.68 KB) Mischa The Evil, 2009-11-24 01:58


Related issues

Related to Redmine - Feature #2889: Separate project field and subject in cross-project issue... Closed 2009-03-03
Follows Redmine - Feature #3100: Better display of subprojects activiry and tickets. Closed 2009-04-02

History

#1 Updated by Mischa The Evil almost 8 years ago

Oops, forgot to actually attach the patch...

edit: also added some relations

#2 Updated by Jean-Philippe Lang almost 8 years ago

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

#3 Updated by Mischa The Evil almost 8 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)?

#4 Updated by Mischa The Evil almost 8 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.

#5 Updated by Mischa The Evil almost 8 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... ;)

#6 Updated by Mischa The Evil almost 7 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.

Also available in: Atom PDF