Bear with me as I'm new to Portfolio and slowly losing my sanity over it...
I've created a few test plans over Portfolio and linked them to existing Epics and stories. So far, so good. However I deleted them as there were test plans and ... nightmare begins...
Since the creation of new tests , I'm trying to link the Epics and stories but I cannot see them anymore!
What happened?
Thanks for any help you might give.
----
update
Please find below the answers to Shannon's questions:
Hey guys,
As requested by Shannon from Atlassian support, please find the answers to her questions below:
Q1: In which project were the Epics and Stories created in?
A1: The epics and stories were created in Jira, not in Portfolio.
Q2: If you happen to have the issue key for those, it will also help.
A2: Hard to explain. My best shot would be the following: Have a look at the video: https://gifyu.com/image/NfAB
A2-1: If you have any questions, please let me know.
Q3: If you have more than one new plan, which plan is it? Have you configured the issue source correctly in order to populate the Epics and Stories?
if he has more than 1 new plan, what is the plan (is the issue source correctly configured to populate these epics or stories)?
A3: You just speak Mandarin to me Joke aside, I have no ideas what you are talking about
Q4: Lastly, are you able to see those Epics and Stories in Jira?
A4: Yes but not all of them. The most recent ones I've created , are not seeable
Best,
Andy
Thanks to Rosario from Atlassian support's team, the issue was due to a filter in the board of Jira itself.
Once the filter has been removed or another board was created without filter, the epics and stories are appearing.
Thanks Atlassion for the swift answer.
Hello Andy,
I'm not 100% sure of what you deleted. In case you deleted stories and epics, once you delete issues from a Portfolio plan, the only way to get them back is by mapping the "Issue source" again.
The steps are:
In case you deleted your plans, you'll have to create again, and in the last step, you will have the opportunity to select the issues you want.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Gabriel,
Thank you for your answer.
The issue is not related to the sources of the data, more why the epics and the stories are not appearing anymore when I'm creating a new plan. I have just updated my ticket with a video, it should be clearer on the issue I'm having.
If you have any questions on my recently updated ticket, please let me know.
Cheers,
Andy
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hey Andy,
Just to confirm, the selection of issues is in the last step when setting up a new portfolio Plan (5th step). When you get there, no issues are appearing?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Andy,
I see that you have also raised a support ticket for this issue.
The information at hand isn't enough to determine the reasoning for the epics and stories not to display, but you can start by providing the following to your support ticket:
In which project were the Epics and Stories created in?
If you happen to have the issue key for those, it will also help.
if he has more than 1 new plan, what is the plan (is the issue source correctly configured to populate these epics or stories)?
Since this thread is public, I advise you only to provide this information in your support ticket.
Once the reason is determined for your missing Epics/Stories, please feel free to provide the details here so it will help future users.
Regards,
Shannon
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Indeed Shannon, I raise a ticket for that as I did not have any feedback from the community, at large. :)
I will put answer your questions in my ticket.
Thanks again for bearing with me as I'm a newbie on Jira.
Cheers.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
No worries, Andy!
I think in this case I think it's likely because those who read your question weren't sure where to proceed without asking specific information that pertains to your Cloud instance. They likely didn't want to have to ask you information that you would otherwise not want to release on a public forum.
Regards,
Shannon
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.