Feature #26488

Project settings : Move issue tracking settings to their own tab

Added by Jean-Philippe Lang 5 months ago. Updated about 1 month ago.

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

0%

Category:Project settings
Target version:4.0.0
Resolution:

Description

I'd like to move a few issue tracking related settings to their own tab in project settings:
  • trackers selection
  • issue custom fields selection
  • default version
  • default assignee

That would make the project form on the first tab a bit cleaner. Unlike now, trackers and issue custom fields would not appear on the new project form but default trackers can now be configured in application settings.

Feedback is welcome.

wiki-page-buttons@2x.png (37.7 KB) Go MAEDA, 2017-07-30 04:12

wiki-rename.png (11.3 KB) Toshi MARUYAMA, 2017-11-05 19:15


Related issues

Related to Redmine - Feature #22090: Make project settings more accessible New
Related to Redmine - Feature #26579: Project settings : remove Wiki tab New

Associated revisions

Revision 16892
Added by Jean-Philippe Lang 5 months ago

Removes the Modules tab in project settings (#26488).

Modules can now be select on the first tab, just like when creating a project.

Revision 16896
Added by Jean-Philippe Lang 5 months ago

Project settings: Move issue tracking settings to their own tab (#26488).

Revision 16899
Added by Jean-Philippe Lang 5 months ago

Hide the issue tracking tab if module is disabled (#26488).

History

#1 Updated by Marius BALTEANU 5 months ago

There are some discussions regarding project settings screen refactorization also in #22090.

#2 Updated by Go MAEDA 5 months ago

Jean-Philippe Lang wrote:

I'd like to move a few issue tracking related settings to their own tab in project settings:
  • trackers selection
  • issue custom fields selection
  • default version
  • default assignee
    That would make the project form on the first tab a bit cleaner.

I agree. There are too many fields in Information tab. However, I am concerned that the number of tabs in project settings will be excessive. There are already 9 tabs.

Unlike now, trackers and issue custom fields would not appear on the new project form but default trackers can now be configured in application settings.

I think it will be a little inconvenient but it is not a big problem because project settings screen will be displayed after creating a project.

#3 Updated by Jean-Philippe Lang 5 months ago

I agree. There are too many fields in Information tab. However, I am concerned that the number of tabs in project settings will be excessive. There are already 9 tabs.

I think we should remove the Modules tab and leave the modules below the project form just like it is when creating a new project.
It would also makes sense to remove the Wiki tab and let the user mark a wiki page as the start page directly from the wiki.

#4 Updated by Jean-Philippe Lang 5 months ago

Jean-Philippe Lang wrote:

It would also makes sense to remove the Wiki tab and let the user mark a wiki page as the start page directly from the wiki.

I think it would actually make the process of changing the start page more straightforward than having go to project settings and enter the title of the start page manually.

#5 Updated by Go MAEDA 5 months ago

Jean-Philippe Lang wrote:

I think we should remove the Modules tab and leave the modules below the project form just like it is when creating a new project.

+1

#6 Updated by Jean-Philippe Lang 5 months ago

The "Issue tracking" tab is now added. What about removing the Wiki tab as proposed above?

#7 Updated by Go MAEDA 5 months ago

Jean-Philippe Lang wrote:

It would also makes sense to remove the Wiki tab and let the user mark a wiki page as the start page directly from the wiki.

What UI do you think?

I am afraid of having too many buttons in the contextual area of a wiki page. There are already 6 buttons and the contextual area is too wide. I am sometimes bothered by wrapped wiki title due to too wide contextual area. It will get worse if another button is added.

#8 Updated by Toshi MARUYAMA 5 months ago

  • Related to Feature #22090: Make project settings more accessible added

#9 Updated by Bernhard Rohloff 2 months ago

Go MAEDA wrote:

I am afraid of having too many buttons in the contextual area of a wiki page. There are already 6 buttons and the contextual area is too wide. I am sometimes bothered by wrapped wiki title due to too wide contextual area. It will get worse if another button is added.

Perhaps, it would be a good idea to hide less used functions in a dropdown menu with a ... button like in #26655.

#10 Updated by Toshi MARUYAMA about 1 month ago

#11 Updated by Toshi MARUYAMA about 1 month ago

Jean-Philippe Lang wrote:

It would also makes sense to remove the Wiki tab and let the user mark a wiki page as the start page directly from the wiki.

FTR: this is done by #26579.

#12 Updated by Toshi MARUYAMA about 1 month ago

Go MAEDA wrote:

Jean-Philippe Lang wrote:

It would also makes sense to remove the Wiki tab and let the user mark a wiki page as the start page directly from the wiki.

What UI do you think?

I am afraid of having too many buttons in the contextual area of a wiki page. There are already 6 buttons and the contextual area is too wide. I am sometimes bothered by wrapped wiki title due to too wide contextual area. It will get worse if another button is added.

r16915 added a checkbox in wiki renaming form.

Also available in: Atom PDF