-1
These things are managed the same way and it makes sense to have a single menu entry.
I don't think that making menus longer is a good solution (we already have 13 items).

Maybe we could add a title attribute on the link so that new users can know what's behind before clicking.
--------------------------------------------------------------------------------
And we can also display items in separate tabs (just like custom fields).
--------------------------------------------------------------------------------
For a user who is unaware of the underlying code structure it is rather confusing to find priorities and activities in the enumerations section but trackers and issue statuses in its own sections.

So I would vote to either:
* Split up the Enumerations into single sections
* Merge trackers and issue statuses into the Enumerations section.
--------------------------------------------------------------------------------
Holger Just wrote:

> So I would vote to either:
> * Split up the Enumerations into single sections

Again, -1.

> * Merge trackers and issue statuses into the Enumerations section.

And why not merging roles, groups... in this section as well?
--------------------------------------------------------------------------------
Jean-Philippe Lang wrote:
> And why not merging roles, groups... in this section as well?

In my eyes, users, groups, roles, LDAP settings and maybe general authentication settings belong together. And this is something other than the enumerations used elsewhere.

What I still can't fit right into this bill are the projects and workflows. They stand right in the middle between all the other stuff...
--------------------------------------------------------------------------------
Jean-Philippe Lang wrote:
> -1
> These things are managed the same way and it makes sense to have a single menu entry.
> I don't think that making menus longer is a good solution (we already have 13 items).

I've setup and directly trained at least 100 people on how to administer Redmine and not a single one of them understands why all of those are grouped into Enumerations. "Enumeration":http://en.wikipedia.org/wiki/Enumeration is a computer science term that is rarely used outside of computer science, so no one knows that menu is where Issue Priorities are configured.

> Maybe we could add a title attribute on the link so that new users can know what's behind before clicking.

A title attribute would only work if a user hovers on the link. I doubt many users would go near it unless told to.

I still think separate menu items is best. I'm willing to pay the cost of 3 more icons on the Admin panel in order to make it really clear where everything is.

--------------------------------------------------------------------------------
Holger Just wrote:
> Jean-Philippe Lang wrote:
> > And why not merging roles, groups... in this section as well?
>
> In my eyes, users, groups, roles, LDAP settings and maybe general authentication settings belong together.

Grouped yes, but not into the sample panel. I've been thinking about adding some style around a few menu items so similar things (like these) are together visually. But still within one click from /admin.

> What I still can't fit right into this bill are the projects and workflows. They stand right in the middle between all the other stuff...

Projects are a major component and should stand alone in my opinion. Workflow is related to Roles more than anything else (connects Issue Statuses to Roles).
--------------------------------------------------------------------------------
I am stepping down from working on Redmine. If someone else is interesting in working on this issue, feel free to reassign it to them.

Eric Davis

--------------------------------------------------------------------------------