In our product, few defects that need fixes from multiple teams like server, UI team etc... We need to capture time spent for each bug. Suppose for a particular bug 3 resources worked to resolve the issue, how they can log time under that bug?
To the best of my knowledge there is no default restriction that limits who can log time against an issue, nor one that restricts an issue to having no more than one person log time against it. For a Company Managed project, you just need to ensure all the people who need to log time against the issue have the right permissions in the project including
- Browse Projects
- Edit issues
- Work on Issues
You don't have to create sub-tasks under the Bug issue for each person in order for each person to log time against the Bug. Doing so, though, might make it easier to track each person's work separately rather than having it all interwoven in the one Bug issue.
Hi Trudy, Your point of view regarding logging hours is correct. Creating task or subtask was to ensure tracking each person works separately.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks @Trudy Claspill for your response. We want to track each person effort to resolve the issue - it can involve Dev, QA, devops team to close the issue. So all of their efforts should be tracked for that day while logging the effort.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Given your other responses that you don't want to add sub-tasks for each person to log time separately, then my original response applies. Each person who needs to work on the Bug can log time directly against the Bug issue using the Log Work option, as long as they have the required Permissions in the project.
If this addresses your question, please mark the response as Answer Accepted to help other community members find the posts that include solutions.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Uttam,
For the bug, Create a main ticket and if multiple people working on it, create sub-task or task so that can track progress and log time.
Hope this helps
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
As suggested by @Vishal Vandre & @Trudy Claspillthere are no restrictions on the number of users logging their work on an issue. The best recommended approach would be for users to create a sub-task for each of them to document their work and to capture their work logs. This way, everyone can log their work on the same bug and the individual work logs are also tracked easily.
Hope this helps!
Thanks!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks for the response @Vishal Vandre and @Bharathi . If we will create another task for a bug - This will add overhead of creating another task for a bug and link that bug to sub-tasks. This workaround is not accepted by most of our team members, so posted this in forum to get any better idea.
Thanks,
Uttam
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.