Why am I suddenly seeing sprints from two separate projects in velocity graph of one of them?

[Malik Alimoekhamedov]

[Bill Sheboy]

Hi @Malik Alimoekhamedov  -- Welcome to the Atlassian Community!

That appears to be an image of a velocity report from a team-managed project.  Is that your project type?

Have you created any company-managed projects in your instance?

Would you please post images of:

• your backlog views of the two different projects, and
• their boards?

Thanks, and best regards,

Bill

[Malik Alimoekhamedov]

Hello Bill,

Thank you for getting back to me on this. Yes, this is a screenshot of a velocity report for one of my team-managed projects (WEBAPP) mixed, for some reason, with another team-managed project (LANDING). See screenshot below.

Interestingly enough, here's the screenshot of the LANDING team-managed project's velocity report:

As you can see, no mixins here.

If that helps anyhow, I did move one of the issues from LANDING to WEBAPP using the 'Move' option. All went well but then this weirdness started happening in WEBAPP.

---

Here are the screenshots you requested:

WEBAPP

LANDING

Thank you in advance for any help you might provide.

[Bill Sheboy]

Thanks for that information!  I read somewhere in this community forum there are plans to add multi-project boards for Team-Managed (next-gen) but that isn't released yet...I think.

Those projects have definitely intertwined.  I saw an open defect about moving a Task to an Epic in another project causing data corruption.  Does that seem related to what happened when you moved the issue? https://jira.atlassian.com/browse/JRACLOUD-76069

If so, there is a work-around noted in the defect.

[Malik Alimoekhamedov]

No, it doesn't seem like it's related but what I did was moving the task that I moved LANDING->WEBAPP back to WEBAPP->LANDING and now my WEBAPP and LANDING velocity graphs look good.
There was clearly some weirdness going on under the hood but your comment gave me a hint, for sure.

Thanks, @Bill Sheboy !

[Bill Sheboy]

If you weren't on a free license, I'd suggest submitting a defect for this one.  As an alternative, I suggest adding a comment to that defect with your additional step/symptoms.  That may help the development team when fixing the problem.  Clearly...moving issues for team-managed projects is creating some side-effects.

Best regards,

Bill