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
Currently, we are in the process of consolidating our projects under a unified product team. I'm seeking assistance in finding a solution to address the following requirements:
I would appreciate your insights on the best possible approach to fulfill these requirements.
Thanks, Trudy for the details.
To add more context to this request let me tell you what we are doing now.
As you can observe, there is a considerable amount of duplicated effort, and when content changes are made, these modifications do not automatically propagate to other projects. To overcome this issue, our team has proposed the following solutions:
Given this situation please provide your recommendation or tell us as to how other companies are using Jira for their product development.
In order for a person (your "customer") to access and update issues in you Jira Software project the users will need to be licensed users of your site/product.
Alternately you could enable Anonymous access, but that would open your site to everybody on the internet unless you can also configure IP Allowlist to restrict traffic from IPs, such as by making your customers access your site through a VPN.
Jira Software projects do not have a "built-in" approval process like Jira Service Management projects. This article provides information on adding an approval step to Jira Software projects: