-
Notifications
You must be signed in to change notification settings - Fork 30
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support for subtasks #16
Comments
@thancock, by the way, @stepashka informs me that child tasks can be closed massively using context menu on subtasks list in parent task window. |
Can you give me an example of such a workflow please, so I can test it? On 07/11/2011 16:53, "Akzhan Abdulin"
|
|
Unfortunately, even with the screenshot it doesn't help me understand this On 07/11/2011 17:07, "Akzhan Abdulin"
|
Is your Redmine has context menus on task lists? It depends on your Redmine version. Context menus were intruduced by Redmine 1.0. |
Yes it sure does. I have: A Main 1Issue - Cross Browser Testing Within that Parent Task I have about 30 child tasks. Types vary; defect, I can see the context menu by hovering over the title, and pressing the I can change the status of one ticket to closed by selecting status > But it's not clear how I would change the status of more than one ticket Thanks for your help! On 07/11/2011 17:45, "Akzhan Abdulin"
|
You can select more than one ticket holding Shift key and choose tickets by clicking on 'em with left mouse button. |
Holding of Ctrl key also works, but in another way. |
Thanks so much for your feedback, I'll take a look at this later today On 08/11/2011 11:08, "Akzhan Abdulin"
|
Hello again, Finally got around to testing this. I am using a mac and this is what I found: Shift key: selects multiple tickets (be in blocks e.g. 1, 2, 3 you can be On 08/11/2011 11:08, "Akzhan Abdulin"
|
Glad to hear this. I suppose that You should create a ticket for Redmine intself to correctly handle other key modifiers (and yes, there is Shift only handled correctly). May be will patched by somebody like me :) |
That's a good point. I might just do that. I look forward to your software On 11/11/2011 12:19, "Akzhan Abdulin"
|
Just cite @thancock:
I was wondering whether you could make an improvement to fix a potential bug and make it even more user-friendly?
An important improvement is the behaviour of the close button when an issue features sub tasks, as there seems to be a minor bug with the current version.
When I have closed all the sub tasks, clicking 'your' close button does not update the status of the button i.e. the close icon remains. I expect the button to behave in the same way when one closes a single ticket i.e. the close button is removed. Instead I must actually enter the issues and then update the issue by saving it (as status will have already been set to closed) or I have to refresh the page.
It would be really helpful (albeit not a higher priority as the aforementioned issue) if the following was supported: enable multiple sub tasks to be closed by pressing the close button once e.g.
a. If sub tasks open >= 1 and the user presses the close button, the user should be warned (via dialog window) that they are about to close all sub tasks.
b. The user can choose from one of two options: OK or Cancel. Clicking 'OK' closes all the sub issues and the current issue clicking 'Cancel' returns the user to their previous state pre dialog window
The text was updated successfully, but these errors were encountered: