You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
We have a governance group that manages multiple projects and reports on progress at the end of each month. We would like to allow developers to manage their projects and their tasks in privacy and only push particular tasks/epics to another portfolio for reporting. Is this possible in jira?
Hi @Rana Abbas and welcome to the Community!
While I don't quite think that letting people work in privacy is the best way to promote teamwork and achieve results together, I can appreciate that your organization may not be at that stage yet.
As long as you let people somehow identify that issues belong to a certain program (through custom fields, labels, ...), Jira's filtering capabilities allow you to retrieve work from different projects for reporting, planning and tracking purposes.
As an example: if you set up a custom field that has a list of your current portfolios, you can easily leverage that to search for all issues belonging to that.
Hope this helps!
Hi Walter! Thank you for the warm welcome. I agree that in an ideal world we should be comfortable opening everything up. However, we find as we start reporting higher and higher in the corporate world, there are lots of details that need to be omitted. One good example of this is technical issues that make sense as milestones for developers might mean very little as a business milestones to project managers and sponsors.
In this case for Jira, people who own the reporting/portfolio, should have at least user access and thus visibility to all the projects. Is that correct?
That is indeed correct. In order to see the issues in Jira, access to the tool is a requirement.