Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature Proposal: Support for Tempo Work Attributes #166

Open
slarti-b opened this issue May 9, 2021 · 0 comments
Open

Feature Proposal: Support for Tempo Work Attributes #166

slarti-b opened this issue May 9, 2021 · 0 comments

Comments

@slarti-b
Copy link
Contributor

slarti-b commented May 9, 2021

I used this app for some time. I haven't recently as we're transitioning to Tempo for work logging within Jira. This means we need to log an Activity Type with each time log. This is a Tempo "Work Attribute" where we choose from a list.

I've tried the Tempo tracker and I don't like it as much as this tool. Yes, once you have an issue open it's just there but I don't always find it reliable. Also, if you have a lot of tabs open it gets lost.

I would like to go back to this tool, but still be able to set the Activity. This means this tool supporting Tempo, to an extent. Tempo is a third party plugin so not everyone has it, but it is pretty widely used and it would be optional. What I am thinking of is:

  • In Settings you could enable Tempo logging instead of Jira Standard (checkbox). It would obviously be up to you to have Tempo installed server-side and so on first.
  • When logging time, if Tempo logging is active it would fetch the list of possible work attributes and offer them (require/offer as configured). It would then use the Tempo API to create the work log entry instead of the Jira standard one

If you don't check the box (which would be default) then nothing should change from now.

I'd be happy to look at doing this, but wanted to check if people were on board before I started.

A couple of caveats

  • We have a self-hosted Jira. I don't have a cloud account to test with. If the Tempo APIs differ there, the support may be limited to hosted solutions unless someone else helps out
  • We only use a work attribute of type STATIC_LIST, so that's what I'd focus on initially. I may be able to support some of the other types, but maybe not all.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant