nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Recommendations / Solution to hide worklog in the project with customers

pmarx

Hi,

We are moving our Jira Software (server) projects to the Jira cloud.

In a few projects, we are working with customers together. We used in these projects the "hide time tracking" application to prevent customers to see the logged work hours.

We track the time with Tempo.

The cloud version of hide time tracking seems not fully compatible in the cloud.

What are your recommendations or solutions to hide the work hours in shared projects?

Do you have good experience with a marketplace app?

Thanks and regards

Philipp

Accepted answers

Alex Koxaras -Relational-

Hi @pmarx

Just a clarification: When you say "customers" you mean other jira users (not JSM customers) to whom you grant access to collaborate, correct?

All comments

Alex Koxaras -Relational-

Hi @pmarx

Just a clarification: When you say "customers" you mean other jira users (not JSM customers) to whom you grant access to collaborate, correct?

pmarx

Yes, I mean other Jira users (not JSM customers).

Alex Koxaras -Relational-

I've crossed check the app you are saying and indeed in the cloud it doesnt seem to exactly do what is promised to do.

With all the info you said, I would suggest to create a clone of each project and sync statuses and comments from one project to another. E.g.

SOLUTION A:

You are working with your devs on project ACTUAL where you log time. You create a duplicate project called COPYCAT, where when you create issues in both projects you "clone" them to other. On ACTUAL, as I said you keep the project among your team. On COPYCAT you give access to your customers. Customers can comment on COPYCAT and you can sync this comment to the other project. When a dev will reply to ACTUAL, then this comment will be transferred to COPYCAT. Of course, on the above scenario you have to link them with a custom field which will be the issue key of the other project.

SOLUTION B:

Another solution would be to grab exalate or a similar app, which has the ability to sync issues. You can instruct exalate, if not mistaken, not to sync worklog but all other stuff, like comments, fields and statuses (both ways).

Dhiren Notani_Exalate_

Hi @pmarx ,

I think you can use a 3rd party issue sync app like Exalate.

With Exalate you can sync issues and also worklogs (if you want) from one Jira instance to another Jira instance, and with the scripting mode in Exalate you get ultimate customizability and control.

Exalate is compatible with Jira Server, Cloud and also Data Center, and with the decentralized architecture that Exalate provides, you get a lot of control over the information that is sent from the source and also the information that is received on the Target.

You may check this guide for understanding how Jira-Jira integration works with Exalate.

Also, please be known that I am associated with Exalate and working with Exalate as a Pre-Sales Engineer.

Thanks, Dhiren

Diana_Architect_ZigiWave

@pmarx hi there! I see Alex has given you a few options to explore. I want to propose another possible solution to your case. ZigiOps is a no-code tool that can help you connect the two Jira instances bi-directionally and sync them (with their data) - you can customize it to sync just the data you want (issues, worklogs, and more). Feel free to check ZigiOps here, on the Atlassian marketplace. And if you want to see it in action (and how it resolves your use case) you can book a tech meeting.

Regards, Diana (ZigiWave team)

Umer Sohail _K15t_

Hey @pmarxhanks for the question! This is Umer from Backbone Issue Sync for Jira's team 😊

As suggested by @Alex Koxaras -Relational- , you can use an Issue Sync app to connect your Jira Cloud instance with your customer's instance, such as Backbone Issue Sync for Jira.

Then you can choose to not sync the time tracking field with your customer's Jira instance, while sharing other required fields and other Jira data like components, labels, custom fields, attachments, and comments. You can also manage the flow of information via uni- or bi-directional control settings and use customized access control settings to ensure foolproof data privacy.

If you have any questions about Backbone or want to get a demo, please get back to us at hello@k15t.com or simply schedule a meeting slot here.

Cheers,

Umer Sohail

pmarx

Hi @AlL :-)

Thank you for your replies.

And would it be possible to sync projects in the same Jira instance?

I have not realized that your solutions syncs the projects to another Jira instance.

We need a solution for customers with the permissions to:

Browse Projects
assignable user
assign issues
create issues
edit issues
schedule issues
transistion issues
create attachments

without any permission to see the logged working hours.

Thanks and regards

Philipp

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

cloud

jira-software

jira-software-cloud

hide

worklog