Hi everyone, hoping that someone can help us resolve the following issue. We have a JIRA project that has the Sprints feature enabled. However, the Sprint context filed is not displayed on the Stories with the project backlog. This is the context field that has the icon that looks like a ship
Hello @Michael Bromley
Welcome to the community.
We cannot see the image you tried to attach to the post.
Are you working with a Company Managed project or a Team Managed project? It will say at the bottom of the navigation pane on the left.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Can you try again to upload the image from your original post? The image is not displaying when I view this post.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thank you, yes, I can.
That image shows that you have added the Sprint field to the context fields section of at least one type of issue in your project. To which issue type did you add it? Can you show us a screen image of the Context Fields section of an issue of that type in that project? Also, can you share an image of the Project Settings > Features page that shows the Sprints option turned on for this project?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Trudy,
That image was taken from our old JIRA board that had the Sprint field already added to the context fields section of Stories and SubTasks. However, we do not know how to add this Sprint context field to our Stories and SubTasks in our new JIRA board.
Below is a screen shot from the Project Settings > Features page that shows the Sprints option turned on for our project in our new JIRA board.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You should be able to go to Project Settings, then select Issue Types.
Then select one of the issue types.
Then drag the Sprint field from the Fields list on the right to the Context fields section in the center.
Then click Save Changes at the bottom.
Then do the same for the other issue types.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Trudy,
We don't get the Sprint field appearing the Fields list on the right, so we cant drag it over to the context fields for inclusion.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Are you working with a Business project, Software project, or Service Management project? It will say at the top of the navigation pane on the left, below the project name.
And, just to confirm, have you had Sprints available in other boards on this Jira instance, for the same type of project?
Also, just to confirm, are you licensed for Jira Software, or only Jira Core?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Trudy, we are working with a Software project which was exactly the same on our old JIRA board.
I don't know whether our new JIRA board is on the same JIRA instance as our old board, I don't think it is.
I don't know whether we are licensed for JIRA Software or only JIRA Core, is that likely to make a difference ?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
If the boards show the same prefix for their URL (https://<yourcompany>.atlassian.net/....) then they are in the same instance.
If the type of project shown at the top of your navigation pane says "Software" then you are licensed for Jira Software in that instance. If you were licensed for only Jira Core it could make a difference, but that is not the case for you.
I am at a loss on this one.
I recommend that you reach out directly to Atlassian Support on this, by opening a support case:
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.