Feature #215
Use Redmine's built-in issue relationships
| Status: | Closed | Start: | ||
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assigned to: |  Mark Maglana |
% Done: | 0% |
|
| Category: | - | |||
| Target version: | Sprint 10.03 | |||
| Story points | 5 | |||
| Velocity based estimate | 8 days | |||
| Remaining hours |
Description
Currently this plugin uses its own method for relating a top-level issue to its children issues. Ideally, it should use Redmine's built-in mechanism for relating issues.
History
Updated by Mark Maglana 8 months ago
- Target version set to Sprint 10
Updated by Mark Maglana 8 months ago
- Status changed from New to In Progress
- Assigned to set to Mark Maglana
Updated by Mark Maglana 8 months ago
- Story points changed from 0 to 5
Updated by Mark Maglana 8 months ago
Here's the plan: I'm going to add two settings to the plugin: TASK TRACKER and TASK RELATIONSHIP. The former will help the plugin determine if an issue is top-level (story) or just a task belonging to a story. The latter will help the plugin determine what sort of relationship a story has to its tasks when a user creates a new one.
Tasks that have no parent stories will be hidden in the plugin.
Updated by Mark Maglana 5 months ago
- Target version deleted (
Sprint 10)
Updated by Mark Maglana 5 months ago
- Target version set to Sprint 10.04
Updated by Mark Maglana 5 months ago
- Status changed from Feedback to Closed
- Target version changed from Sprint 10.04 to Sprint 10.03
Closing.