Welcome to Tempo’s Idea Portal! Your suggestions are valuable to us and help us make our products even better.
Below is a list of ideas for Tempo, so please search, review and vote for those that would help you the most. We encourage you to add an idea if you don’t see it listed. You can stay updated on the work we are doing here at Tempo by contributing to this page.
To learn more and see our Frequently Asked Questions, click here.
Tempo has matching dates, potentially different for each resource assigned to this particular Jira issue:
Plan Start and End
Logged time - dates for First and Last time cards posted by staff
Can we do it such, that the start time in Tempo of the chronologically first staff member planned to work on a particular issue, would be automatically reflected in Jira as a Planned Start date. Likewise, end of the chronologically last staff member planned to work on this issue in Tempo, would be reflected as the Planned End date in Jira.
Similarly, when staff members start logging their time in Tempo against this particular Jira issue, start of the chronologically first such time logged needs to be reflected in Jira as [Actual] Start Date. Likewise, end of chronologically last time logged by the “latest” staff in Tempo needs to be reflected as [Actual] End Date in the Jira issue.
Stefanny Alarie
Each our issue in Jira has 2 pairs of dates:
Planned Start and End Dates
[Actual] Start and End Dates
Tempo has matching dates, potentially different for each resource assigned to this particular Jira issue:
Plan Start and End
Logged time - dates for First and Last time cards posted by staff
Can we do it such, that the start time in Tempo of the chronologically first staff member planned to work on a particular issue, would be automatically reflected in Jira as a Planned Start date. Likewise, end of the chronologically last staff member planned to work on this issue in Tempo, would be reflected as the Planned End date in Jira.
Similarly, when staff members start logging their time in Tempo against this particular Jira issue, start of the chronologically first such time logged needs to be reflected in Jira as [Actual] Start Date. Likewise, end of chronologically last time logged by the “latest” staff in Tempo needs to be reflected as [Actual] End Date in the Jira issue.