Enumerations and Best-Practices Values

Added by Markus May over 9 years ago

For the enumerations in Redmine, it would be great, if you would provide Best-Practices Values. So e.g. for the Document Categories something like User Documentation, Technical Documentation, ...

I think some default best-practices values would provide much better usability for new users.

What do you think? Should I open a feature for this?

Replies (3)

RE: Enumerations and Best-Practices Values - Added by Markus May over 9 years ago

Probably this should be done via a Best-pratices documentation?

I would suggest right now the following values:

Documentation:

User Documentation
Technical Documentation
Analysis
Requirements
Technical Design
Functional Design

Ticket Priorities:

High
Medium
Low

Ticket States:

New
Open
Closed

Roles:

Non-Member
Anonymous
Comitter
Contributor

What do you think? any further suggestions?

RE: Enumerations and Best-Practices Values - Added by Markus May over 9 years ago

I wanted to start a discussion here, what values are needed for different projects (e.g. Open Source, Closed Source Commercial, ...) and what works best for you. I know already, that some basic values can be filled with the specific rake command

rake redmine:load_default_data RAILS_ENV="production" 

But still, I think that this could be improved for different environments. What are your thoughts?

Anyway, redmine is a very nice project and we are going to use it in the company i am working for as soon as I get the new server :-)

RE: Enumerations and Best-Practices Values - Added by Rachid Otsmane over 9 years ago

It would be better to analyse what how your project is currently run, for instance what states can issues be in currently and transfer these into Redine itself. Same with Roles, what are the actual roles people have on your project? If some of these require the same access but have different names, I'd still handle them individually, not only for clarifications sake, but also for scalability

(1-3/3)