Tempo Ideas

I would like Tempo or the Tempo Calendar Apps to add support for an optional, configurable, per-project alias that would be recognized by the app when scanning calendar event titles for valid Jira issue keys. To simplify the implementation, this alias could become the only thing searched for, instead of having to search both the original project name and alias.

I.e. For Project name MYSYS and Issue Key MYSYS-99, the user configures an abbreviated project alias MS in the Tempo configuration. To import the issue into tempo, a calendar event title would need to include MS-99 (and/or MYSYS-99). This provides flexibility in the text that must be embedded into often-highly-visible calendar events when using this app.

Rationale:

1. Tempo integration with Google and Office365 calendars require the Jira issue key to appear verbatim in the calendar event title.

2. There are numerous use cases where this requirement is unreasonable, because the audience/scope of a meeting invite is generally independent of and unrelated to any Jira project that needs to be associated with the meeting, i.e. meeting audiences may not be privy to the information that may be embedded inside the Jira project name, e.g.

   1. the name of a consulting firm is in the Jira project name that the consulting team uses for PM.

   2. the consulting team uses Tempo for time tracking and syncs their Google Calendar to automatically associate client meetings with a long-running Jira Issue.

   3. the client calls meetings with an audience, e.g. another firm, that it doesn’t want to know that the client has hired this consulting firm.

3. Jira allows changing the project name, but this is cumbersome and eliminates the positive side-effect of having project name recognition internally.

4. Jira doesn’t allow project aliases natively.

Thanks for your consideration.