Bug Tracking Software Resources

In our team, we never use jira to track the informal things. Accounting for non-productive or administrative tasks is part of agile planning. The way agile was planned in our team was to allocate 1-2 hours everyday for scrum, meetings and other events .. so average weekly availability for each developer was ~ 30 to 32 hrs of 40 hrs (considering an 8 hour work day per week). All tasks for the stories were planned according to the adjusted availability which allowed us to not over/under commit better.

Show More

Show Less

you dont need to track informal meetings in Jira. We are tracking deployments, test status and of course in case of issue TR will be opened. We have agile boards for PDU,SI,SA,SV teams which help management visibility in terms of tracking work

Show More

Show Less

JIRA isn't designed to track meetings and is mostly used for tracking issues, bugs, deployment, etc. This acts as a ticketing system where you have a request# associated with any change, and you should track the hours only worked on that request. If you wish to track the timecards throughout the day, the Salesforce application leverages this option in the best possible way. As a note, you can make use of Atlassian Confluence which allows you to track your meetings (formal/informal) along with action items decided in the current meeting. Also, these action items can be referred to recurring meetings as follow up and mark those as completed or blocked. You also can tag users based on action items or notes.

Show More

Show Less