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
At the Adv Roadmap Plan, I created some test Initiative/requirements at the SCOPE level with the "+Create Issue" button. I was able to move some stories underneath using drag&drop.
I then try to click on the link of the initiatives that I create. I can see the summary/title. However the issue-key part only has my project's prefix, it does not have the issue number. So when I clicked on that link, it took me to my board, which was the input source.
Then I tried to search for those in my project but couldn't find it. It is definitely somewhere in the system... since the Plan has them in the "parent" dropdown.
As a reverse test, I created a Requirement in my project using the standard blue "Create" button. After a short wait, my newly created requirement issue-key(full) did show up in the dropdown for possible "parent"
In AR you need to commit your change 'on the top right' in order to have them pushed to JIRA. Otherwise it will exist only in AR not JIRA. That's why there is no number as issue key, the issue is not create in JIRA yet.