Project

General

Profile

Actions

task #6004

closed

Fix wiki page Roadmap

Added by Andreas Kohlbecker almost 7 years ago. Updated over 6 years ago.

Status:
Closed
Priority:
New
Category:
devOps
Target version:
-
Start date:
Due date:
% Done:

100%

Estimated time:
Severity:
normal

Description

The trac query macros which have been used in trac need to be replaced by equivalent functionality in redemine:

Query macros for Roadmap page and others:

Actions #1

Updated by Andreas Müller almost 7 years ago

  • Assignee set to Andreas Kohlbecker
  • Target version set to Release 4.3
Actions #2

Updated by Andreas Kohlbecker almost 7 years ago

  • Status changed from New to Resolved
  • Assignee changed from Andreas Kohlbecker to Andreas Müller

I found a solution by making use of the redmine_wiki_lists plugin
This macro

{{ref_issues(-q:Release4.2 , id, subject, status)}}

results in the display of the issued found by the saved custom query Release4.2 in form of a table

The result is actually more space consuming compared to what we had in trac, but it is the only straight forward solution i found.

Other options could be:

  1. Write a plugin
  2. Use the http://www.redmine.org/plugins/advanced_roadmap or https://github.com/Coren/redmine_advanced_roadmap_v2 plugins.
  3. https://github.com/hdgarrood/redmine_release_notes
  4. https://github.com/k41n/redmine_milestones

Separating out Milestones from Releases would make the build-in Roadmap Views more clear and focused on versions. Using redmine_release_notes together with a plugin which supports milestones could be nice solution, but maybe much more work to maintain.

Andreas Müller: please review

Actions #3

Updated by Andreas Müller over 6 years ago

  • Category set to devOps
  • Status changed from Resolved to Closed
  • Assignee changed from Andreas Müller to Andreas Kohlbecker
  • Target version deleted (Release 4.3)
  • % Done changed from 0 to 100

This looks good to me. the result looks very similar to what we had before and to have the status also available is an advantage I think. This way developers can easily find out if there are e.g. duplicates still handled in the milestones though they shouldn't.

The alternatives do all have drawbacks as either the projects are not maintained anymore or they do not allow as much configurability as our current solution.

I think we can close this ticket.

Actions

Also available in: Atom PDF