Feature #29470
openPossibility to mark tracker as "Subtask only"
Added by Kamil . almost 6 years ago. Updated 10 months ago.
0%
Description
There are some types of trackers (like "Story Blocker" or "Subtask") which makes sense only when it is a subtask.
Please provide additional checkbox "Subtask only" while creating new tracker.
When checked, new item can be created only as a Subtask
Files
tracker_subtask.png (52.6 KB) tracker_subtask.png | Marius BĂLTEANU, 2019-06-30 23:36 | ||
workflow.png (238 KB) workflow.png | Marius BĂLTEANU, 2019-06-30 23:38 | ||
new_issue.png (87.5 KB) new_issue.png | Marius BĂLTEANU, 2019-06-30 23:43 | ||
0001-Option-to-set-a-tracker-only-as-subtask.patch (20.1 KB) 0001-Option-to-set-a-tracker-only-as-subtask.patch | Marius BĂLTEANU, 2020-04-05 13:26 | ||
Option-to-set-a-tracker-only-as-subtask-r20091.patch (17.9 KB) Option-to-set-a-tracker-only-as-subtask-r20091.patch | Go MAEDA, 2020-09-28 10:12 |
Related issues
Updated by Marius BĂLTEANU almost 6 years ago
- Is duplicate of Feature #27988: Option to configure which trackers can be set as subtasks for each tracker added
Updated by Marius BĂLTEANU almost 6 years ago
- Status changed from New to Closed
- Resolution set to Duplicate
Please see the related issue.
Updated by Kamil . almost 6 years ago
My request is related to, but it is not the same as Feature #27988.
In my feature the idea is that some trackers must not be top-level trackers
Updated by Marius BĂLTEANU almost 6 years ago
- Resolution changed from Duplicate to Invalid
Kamil . wrote:
My request is related to, but it is not the same as Feature #27988.
In my feature the idea is that some trackers must not be top-level trackers
Kamil, I've closed this ticket as "Duplicate" because you can obtain the same behaviour as you requested in this issue using the patch from #27988.
Thinking now better, you can obtain this behaviour also with the current Redmine versions by making the "Parent task" field mandatory for all roles in the Workflow page (I know that is not a checkbox, but the result is the same). I'm changing the reason from "Duplicate" to "Invalid", please let me know if you consider that something is missing and I'll reopen it.
Updated by Marius BĂLTEANU almost 6 years ago
- Is duplicate of deleted (Feature #27988: Option to configure which trackers can be set as subtasks for each tracker)
Updated by Marius BĂLTEANU almost 6 years ago
- Related to Feature #27988: Option to configure which trackers can be set as subtasks for each tracker added
Updated by Kamil . almost 6 years ago
Marius, why to complicate is so much?
Do you consider your solution as good UX?
Updated by Marius BĂLTEANU almost 6 years ago
Kamil . wrote:
Marius, why to complicate is so much?
Do you consider your solution as good UX?
Do you refer at the solution with setting the parent task mandatory?
Updated by Kamil . almost 6 years ago
Yes, specifically:
1) Knowing that you have to go to Workflow
2) Field Permissions
3) Select Role "ALL"
4) Select Tracker
5) Click Edit
6) Find "Parent task row"
7) Click and select value "Required" in each Issue status
8) Click save
Updated by Kamil . almost 6 years ago
So my point is that your version is not user friendly and doesn't have user intention in mind.
I think that every tool should strive to have better UX, therefore I created this issue
Updated by Marius BĂLTEANU almost 6 years ago
- Status changed from Closed to Reopened
- Resolution deleted (
Invalid)
Is not my version, is the current implementation from Redmine which is more flexible than having only a checkbox in the Tracker page.
IMHO, current implementation, plus the feature from #27988 covers this feature request, but I'll reopen this ticket to get more feedback.
Updated by Marius BĂLTEANU about 5 years ago
- Assignee set to Marius BĂLTEANU
- Target version set to Candidate for next major release
Updated by Marius BĂLTEANU about 5 years ago
- File 0001-Option-to-set-a-tracker-only-as-subtask.patch added
- File tracker_subtask.png tracker_subtask.png added
- File workflow.png workflow.png added
- File new_issue.png new_issue.png added
- Assignee deleted (
Marius BĂLTEANU)
Attached a patch that adds the possibility to mark a tracker as "Subtask only":
In the workflow, if the user edits a a tracker or multiple trackers which are "Subtask only", the field is marked as mandatory and the option "Required" is not available. If the user edits mixed trackers, the field behaves normally.
The field "Parent task" is mandatory when user tries to create an issue with tracker type "Subtask only":
Updated by Marius BĂLTEANU almost 5 years ago
- File deleted (
0001-Option-to-set-a-tracker-only-as-subtask.patch)
Updated by Marius BĂLTEANU almost 5 years ago
- File 0001-Option-to-set-a-tracker-only-as-subtask.patch added
- Assignee set to Jean-Philippe Lang
- Target version changed from Candidate for next major release to 4.2.0
I've updated the patch to apply cleanly on the current trunk and I'm assigning this to 4.2.0 in order to work on this as early as we can.
Updated by Marius BĂLTEANU over 4 years ago
- File deleted (
0001-Option-to-set-a-tracker-only-as-subtask.patch)
Updated by Marius BĂLTEANU over 4 years ago
- File 0001-Option-to-set-a-tracker-only-as-subtask.patch 0001-Option-to-set-a-tracker-only-as-subtask.patch added
Updated again to apply cleanly.
Updated by ashraf alzyoud almost 4 years ago
Marius BALTEANU wrote:
Updated again to apply cleanly.
its very important i have 30 tracker in same project
our users need who main tracker and sub
thx for u for this idea
this patch available in 4.1??
Updated by Go MAEDA almost 4 years ago
- File Option-to-set-a-tracker-only-as-subtask-r20091.patch added
Updated the patch for the latest trunk (r20091).
Updated by Go MAEDA almost 4 years ago
- File deleted (
Option-to-set-a-tracker-only-as-subtask-r20091.patch)
Updated by Go MAEDA almost 4 years ago
Updated by ashraf alzyoud almost 4 years ago
Is there a possibility to hide the subtask trackers when in added newIssue?? and its appear only when im added subtask??
Updated by Marius BĂLTEANU over 3 years ago
- Target version changed from 4.2.0 to 5.0.0
Updated by Marius BĂLTEANU over 3 years ago
Moved this to 5.0.0 because the changes are quite big.
Updated by Marius BĂLTEANU over 2 years ago
- Target version changed from 5.0.0 to Candidate for next major release