Feature #23287
Better structuring of Version page
| Status: | New | Start date: | ||
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assignee: | - | % Done: | 0% | |
| Category: | Roadmap | |||
| Target version: | - | |||
| Resolution: |
Description
Quite often version itself represent a specific scope of work under the large project or a full project itself and hence it should be reflected in the version page.
Specifically the version page should have following information.
- % completion and color coding of issue listing based on status.
- Tree structure of issue listing based on sub-task
- Allow to order the issues (not necessarily sort by tracker or issue number) which represent the order of work or any other criteria.
- List of users involved in the version (based on assigned users of issues under the version).
- Similarly show followed/precedes relation of issues through arrows that will map flow of work more elegantly.
Related issues
History
#1
Updated by Dipan Mehta over 2 years ago
Add related - #4992 which also talks about better printable layout of version page.
#2
Updated by Toshi MARUYAMA over 2 years ago
- Related to Feature #4992: Add printer friendly version of pages added
#3
Updated by Toshi MARUYAMA over 2 years ago
- Related to Feature #13387: Improving Redmine's version model (not just milestones) added
#4
Updated by Alexander Lyzhenkov about 1 year ago
+1
#5
Updated by Marius BALTEANU about 1 year ago
Dipan Mehta wrote:
3. Allow to order the issues (not necessarily sort by tracker or issue number) which represent the order of work or any other criteria.
A patch that implements this feature is in #22802.
#6
Updated by Marius BALTEANU about 1 year ago
- Related to Feature #22802: Add the posibility to set/change the position of an issue in a version added
#7
Updated by Dipan Mehta about 1 year ago
Marius BALTEANU wrote:
Dipan Mehta wrote:
3. Allow to order the issues (not necessarily sort by tracker or issue number) which represent the order of work or any other criteria.
A patch that implements this feature is in #22802.
This is brilliant! Thanks a lot.