We are evaluating Tempo planner for Agile Sprint planning and it seems like planning is not assigning issues to the end users, can some one explain the process of this. Is that,
1. I need to plan based on availability of the hours for the users and then if plans are approved then I need to manually assign the same for the individuals ?
2. I see latest version of tempo has removed all backlog and Iteration features ? Is there any specific reason for the same.
Let me know if you have any questions regarding the same.
If you already heard about Smart Commits in Bitbucket, know that you just stumbled upon something even better (and smarter!): Genius Commits by Better DevOps Automation for Jira Data Center (+ Server...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events