Hi akavelar,
hi pglantschnig,

thanks for following up on this issue.

• I only have one field configuration – default field configuration – which is shared by all projects. The fixVersion field is enabled for all issue types.
• The issues not showing up are of type Story and Epic.
• They come from different projects.
• I cannot confirm that the field was already enabled for these issues at the time they have been created, because it was up to two years ago. However, as I'm only using the default field configuration, it might have been enabled since the beginning.
• While trying out some approaches, I performed a re-index multiple times.

I just tried out to remove the Later release from an Epic. Once I did so, it immediately disappeared in Live Plans. Once I re-added it, it shows up again. So I think its not a matter of an enabled/disabled fixVersion field. It's just enough to leave the enabled field empty.

If you need more information about my configuration, I'll be very happy to support you in order to get to the bottom of this.

I already raised a support ticket where I was pointed to this issue.

Cheers,
Stefan

Hi stefan.hennig,

as akavelar just mentioned, it could be a different problem.
Can you confirm that the fixVersion field was already enabled for your issues at the time they have been created? If not, it could be that the index was just outdated, so it might be necessary triggering a re-indexing after adding the fixVersion field.

Probably you could try to remove your custom "Later" release from an issue again and see if it still shows up in your Portfolio Plan.

Cheers,
Paul
Portfolio for JIRA Development

Hi stefan.hennig,

thanks for your reply and the additional information. Just to clarify - you have the fixVersion field enabled on for all issue types as well? Were the issues not showing up all of the same type? Where they all coming from the same project?

It sounds like you might be facing a different issue than this one, could you raise a separate support ticket here so we can follow up on it and get to the bottom of it?

Thanks,
Best regards,
Albert Kavelar | Portfolio for JIRA Development

Hi!

I was faced with a quite similar behavior. We are using the fixVersion field, it is enabled for all our projects, but some issues without a concrete version assigned were not shown in the Live Plans. The curious part is, that other issues without a fixVersion assigned are shown.

I was able to fix that behavior by assigning a concrete version to all issues. Those issues without a fixed schedule got a "Later" release. Only with this workaround, I was able to see all issues in the Live Plan.

Cheers,
Stefan

This one caught us too. Many of our projects don't bother with versions, especially when we're using them for non-software projects.

Hi thagen,

thanks for the update. Too bad we no longer have the plan where the problem occurred. Anyway, we are happy to help you out with the other problems you have and suggest to file new tickets here since they are probably unrelated to the original issue you reported on the hidden fix version field.

Thanks,
Best regards,
Albert

Hi, Martin and Albert: Sorry for the delay. Unfortunately, the product owner who was testing this behavior has reverted to the traditional plan and deleted her Live plan, so I can't confirm. However, it's safe to say that we were using neither releases nor subtasks. Instead, I'd like to loop in one of our other product owners, Jon Hill, who has some related scheduling questions and suggestions – perhaps best addressed in new issue(s)? Thanks.

Hi thagen,

any updates on the questions msturm@atlassian.com asked in his last comment? Did you find the time to look into this?

Best regards,
Albert Kavelar | Portfolio for JIRA Development

Hi thagen,

thanks for providing the additional information. There is nothing too suspicious though.. I also do not think it's related to the issue in the group, because there was only some confusion about how we filtered the solution on different hierarchy levels.

Can you please verify that this plan doesn't use any releases? Having issues assigned to releases with dynamic end date might change the priority of this issue because we try to schedule it as soon as possible in order to minimize the dynamic release date.
The other possibility would be that this is another case of our scheduling with subtasks problem: https://jira.atlassian.com/browse/JPO-1323
I do not see any subtasks in the table though, right?

Thanks, Martin

Hi Martin,

We are on Cloud: 1.12.2.
We are using Rank: ORDER BY Rank ASC
We are only using one board for the project.
The order of the issues in the Scope table does not change on refresh.

If you are unable to reproduce, then we can work around this for now. In fact, I think our product owner has tried starting over with a new plan, so I'm not sure if this is still impacting us. I also thought this might relate to the same issue: https://www.linkedin.com/groups/7018171/7018171-6106451939954880515

Thanks for the reply,
Tim