Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
Next:
badges earned

Your Points Tracker
Challenges
Leaderboard
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Recognition
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Kudos
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

How to avoid having two "log work" options when using Tempo

I'm currently testing Tempo and have stumbled over the problem that after installation two "log work" options with the same name appear under the issue screen action buttons and in other places - one opening the default JIRA work log dialogue, the other opening the Tempo mask. This is very confusing. As we require work log attributes, it would be mandatory for us that all create and edit operations in all places only use the Tempo mask. I have already studied a couple of discussions around this topic (https://answers.atlassian.com/questions/169634/disable-jira-standard-work-log-dialogueand https://answers.atlassian.com/questions/167668/two-work-log-options-showing-up), but it seems that the workaround suggested does not solve the problem for other places like the issue navigator, is that correct? Does that mean that Tempo is not able to replace or hide the JIRA dialogue instead of adding a second one, is that not possible or do you see any benefit in having two different dialogues? How can I prevent my users from using the "wrong" mask?

2 answers

You can dsiable the following module under Issue Operations Plugin:

View Issue Ops Bar Work Link

(log-work)

You can do it from UPM > System Add-ons.

I know that. But when I deactivate the log work module in the "Issue Operations Plugin", this surprisingly also deactivates the "Log Work" tab and the "Time Tracking" panel on the issue screen. So I can't see estimates any longer and do not have an option to edit work logs (or to see/update work logs of others) from the issue screen. Is there someone from the Tempo team able to answer my original questions?

But when I deactivate the log work module in the "Issue Operations Plugin", this surprisingly also deactivates the "Log Work" tab and the "Time Tracking" panel on the issue screen. So I can't see estimates any longer and do not have an option to edit work logs (or to see/update work logs of others) from the issue screen

That shouldn't happen. I have done it succesfully in different versions including 6.2.7 which is my current version.

Maybe I am missing something here. And hopefully some one else can help you figure it out.

I'm using JIRA 6.2.4 for testing. Have now tried in another demo instance (version 6.2), and here the behaviour is like expected, tab and panel are not deactivated. So this just seems to be a bug in JIRA 6.2.4.

Hello We actually use JIRA 6.2.7 and Tempo 7.10.1. But I do not see the plugin 'Issue Operations Plugin'. Do i have to install this seperatly? Thanks for your help.

I saw the plugin yesterday deactivated and re-activated the log work module and the the plugin disappeared. I don't see it anymore. Reindexing, delete local cache, log out and login again did not help. The plugin is simply not there anymore. Need help! Using Jira 7.2.7.

We are actually using Jira 8.4.1 and the 'Issue Operations' Plugin is not available. Has anyone else had the same experience? I would like to disable the log work option.. and it seems like this is the only way but with Jira 8.4.1 it doesnt work..

->Update: Found my mistake.. I translated Jira to my mother tongue and I would say 99% of the plugins were displayed in english, so I searched for the english plugin title, but 1% - including "issue operations" - were translated. So it was a classis PEBDAC

Suggest an answer

Log in or Sign up to answer
TAGS
Community showcase
Published in Marketplace Apps & Integrations

Jira issue check and more advanced commit verifications for Bitbucket DC

Pre-receive hooks that verify the Git commit message, the modified files, and implement similar code change controls used to be requirements of large enterprises working in regulated industries only....

55 views 0 3
Read article

Community Events

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

Events near you