At the beginning of every Sprint you could set up a separate Story (or other issue type, maybe a Spike or Pink Card) to track time for meeting notes. This would also give you a good break down of how much time is spent each Sprint.
If you use sub-tasks you could also have each person create their own sub-task to get a good visualization of who spent time on meetings each Sprint.
Hope this helps,
Not really. The problem is that you really want to record time and the only way that counts in Jira is a work log on an issue. Doing anything else means Jira won't know about it.
A lot of places log one "meeting" issue per sprint, or, when they have a regular cadence (e.g. planning + standup + retrospective all add up to 4.5 hours for everyone in each sprint on average), ignore the tracking completely, as it's simple overhead.
I’m a designer on the Jira team. For a long time, I’ve fielded questions from other designers about how they should be using Jira Software with their design team. I’ve also heard feedback from other ...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs