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
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
Requirement or a Use case -
there was project in Old JIRA and as users complain that its not sufficing there need, we created same project in NEW JIRA with different configuration.
As we are working on Agile frame work, when a user selects the project in old jira can it open the project in new JIRA. so that issues can be created in new instead of old.
What are the possible options can JIRA provide in such scenario.
Case study - I have (1A to 10A) projects in Old JIRA (ABC.com) .1 project ( 1L ) in New Jira (XYZ.com)
Now the user want to access new jira with old jira. The old jira is not retiring but would like to go live with what we have so far in new jira.
Now the ask is, I will log in ABC.com and can access 1A to 10A projects but instead of 9A project in old jira that needs to open the 1L project in new jira. what ever is created in 1L has to be created in new jira only, we dont want large audience to switch around the urls but using the old jira (ABC.com) and instead of 9A old project in old jira has to be now 1L (new project) in new jira (XYZ).
Hope the above scenario gives you more detail view of the ask
Yes, this is a perfect use case for a redirect on reverse proxy level.
Here an example for the popular Apache webserver.
RewriteRule "^/browse/OUZEL(.*)$" "https://mynewjira.example.org/browse/MAGPIE$1" [R,L]