Understanding Tempo Cards in My Work

Tempo time cards provide you with lots of information, all in one place. This includes the activity title, description, provider (or source) of the activity card and the amount of time that was estimated to have been spent on an activity. We have two types of cards, an activity card and time record.

Activity Card:

Activity_card_with_callouts_copy-1.jpg

In the example above, the Tempo administrator has set the title of the activity, Jira issue key, and time spent as the required fields. Your activity card may differ based on what your Tempo administrator sets your required fields to be.

Types of cards:

  • A logged time record is greyed out and has been logged in with all its required fields completed.

    Time record
  • A complete Activity card for a single provider is one that has all the required fields filled in and is ready to be logged as a time record.

    complete_Activity_card.jpg
  • A complete Activity card that comes from more than one provider but belongs to the same Jira issue that the user worked on simultaneously. This shows up with a lightning bolt icon. You can view the activity providers by hovering over the lightning icon.

    Activity_from_multiple_provider.jpg
  • An incomplete activity card is outlined in orange and is missing some required fields to transform the activities into a time record. Hovering over the orange triangle will display a list of what you’re missing to log time on the issue.

    • For example, let’s say you want to log time towards a meeting but the meeting organizer forgot to include the issue key (a required field) for the meeting, then the activity will appear outlined in orange. You will have to enter the issue key to log time.

      Incomplete_actiivty_card.jpg
  • A Plan time card appears when you have planned activities in either My Work or Tempo Planner.

    Plan_time_card.jpg

Note

Consecutive events with the same Jira issue key will appear as two individual activity cards. This will help to distinguish and specify the work that was done under the same Jira issue key.

For example, if you have meetings with the Jira issue key CLOUD-47 (general Jira issue key for meetings) from:

  • 9:00 AM to 9:15 AM for a standup meeting with your time

  • 9:15 AM to 10:00 AM for a sprint retrospective meeting

Then, these events will appear as two activity cards even though they share the same Jira issue key.

Note

The required fields (e.g., Jira issue key, description, remaining estimate) are set by the Tempo Administrator.