nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

When creating a story in an upcoming sprint it gets put into the backlog

Keith Francis_pvi3iv

We are using a company managed project using different board to see what different teams are working on. The problem is when I create a story in an upcoming sprint it places it into the backlog and not into the sprint that I created the story in.

Any ideas why this happens in the company managed projects. If i use a team managed project it works fine.

Thanks in advance

Accepted answers

Keith Francis_pvi3iv

After some initial troubleshooting here is the solution

This is caused if there is a custom field, by the name "Sprint". This conflicts with the Jira system field "Sprint". The system field will be Locked state. From further investigation, there is a Sprint custom field in project "something project" which has the same custom field name as the Jira system field. Edited this non-Locked "Sprint" field and rename it to "Sprint Duplicate". This step fixed this problem. This issue was caused by a bug.

All comments

Trudy P Claspill

Hello @Keith Francis

Can you provide more details on how you are 'creating a story in an upcoming sprint'?

In my case I have a company managed Software project with a board that has a filter that picks up all issues in that one project. On the Backlog screen, when I click on the Create Issue option directly below an unstarted sprint, the resulting new issue ends up in that sprint.

Screen Shot 2021-11-11 at 2.35.22 PM.png

Keith Francis_pvi3iv

Create story in sprint.JPG New Story placed in Backlog.JPG

Keith Francis_pvi3iv

so when i create THIS IS A TEST STORY in New Story in OT AD Sprint 2 it creates it in the backlog and not in the sprint that it was created - see highlighted text above.

Trudy P Claspill

So far I have not been able to recreate the behavior you see, in my own Jira Cloud instance.

Are you able to drag the new issue from the backlog into the sprint?

Do you have the Schedule Issues and Edit Issues permissions in the project(s) referenced by this board? I'm looking at the information on the following page under Manage Sprints, under the collapsed section within that for Notes On Working With Sprints.

https://confluence.atlassian.com/adminjiraserver073/managing-project-permissions-861253293.html

Keith Francis_pvi3iv

After some initial troubleshooting here is the solution

Trudy P Claspill

I never thought about the duplicated field. Good find!

Nic Brough -Adaptavist-

Not a bug, then, but a mis-configuration!

Nicely found though, that's not an easy one to spot!

Keith Francis_pvi3iv

Thanks Nic - we have now confirmation from the Atlassian team who have plans to fix this "bug" or block team-managed projects from using system field names as it looks like it is highly likely to happen again.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

cloud

jira-software

jira-software-cloud