I’m trying to set up Jira for a client project and I’m not sure how to handle task visibility. Here’s what I want to do:
Create high-level tasks like Design, Development, and QA
Make these main tasks visible to the client
Allow my team to create subtasks under each main task
Keep these subtasks hidden from the client
Is there a way to configure Jira so that clients can only see the parent tasks but not any of the subtasks? I want to keep the nitty-gritty details of our work process private while still giving the client an overview of the project progress.
Has anyone done something like this before? Any tips or tricks would be super helpful. Thanks in advance for any advice!
hey charlieLion, i’ve done somethin similar before. you can use Jira’s permission schemes to restrict client access. create a separate project for client-facing tasks and link em to your internal tasks. that way, clients see the big picture without all the details. it takes some setup but works great!
As someone who’s managed numerous client projects in Jira, I can relate to your dilemma. One approach that’s worked well for me is using a combination of issue types and custom fields. Here’s what I did:
I created a ‘Client-Visible Task’ issue type for the high-level tasks. Then, I set up a custom field called ‘Client Progress’ on these tasks. My team updates this field regularly with a summary of progress, which is what the client sees.
For the nitty-gritty work, we use standard tasks and subtasks, linked to the client-visible tasks but not directly accessible to clients. This way, we maintain our detailed workflow internally while providing clients with a clean, high-level view of project progress.
It takes some initial setup, but it’s been a game-changer for managing client expectations and internal processes simultaneously. Hope this helps!
I’ve implemented a similar setup for client projects. One effective approach is utilizing Jira’s issue security levels. Create a security level for client-visible items and apply it to parent tasks. Then, configure permissions so your client’s user group can only view issues with that security level. This keeps subtasks hidden while allowing clients to track overall progress.
For more granular control, consider creating a separate board or filter view specifically for client interactions. This can display only the high-level tasks, providing a clean, simplified overview of the project status without exposing internal workflow details.
Remember to thoroughly test your configuration before granting client access to ensure no sensitive information is inadvertently exposed.