You might be using a Next-Gen project where the Release feature is not enabled. Please go to the Project Administration -> Features and enable Releases.
In Next-Gen projects, it is possible that Sprint feature is disabled. See above for the same problem with the Release feature. If you are using a Classic Project (or using Server or Data Center), the selected agile board might not support Sprints or you do not have Manage Sprints permission.
The selected agile board contains more than one project. You need to have Manage Sprints permission in all included projects.
Make sure the sprint field is visible on the edit issue screen. If you created your project from a template that is not the scrum template, you need to add this field manually.
You might have had this issue in a previous sprint and that sprint was completed. Unfortunately, Jira does not clear the sprint field even when the issue is moved back to the backlog and / or is still in an open or in progress state. You need to manually reopen the old sprint and clear the field. See here for more info.
If you have more than 1 project in your story map, you will see the release versions of all projects. But you can only assign the issues from one project to fixVersions of the same project. There is unfortunately nothing we can do about this.
If you want to plan cross-project releases, we recommend you use the custom timeframe feature, available in the pro version.
There are unfortunately several reasons for this:
- The configured board is a scrum board but the context for the story points field does not include the current issue type. See this community thread for further info.
- The configured board is a Kanban board or no board is configured and you have enable the estimation feature via Story Mapping app - you need to make sure the story point field is available on the edit screen of the issue type.
- You entered an invalid value for the field. Story Mapping app will try to cast any value to a number but this can fail.
Currently only Software Projects are supported in the free edition (the Pro edition supports all project types). You won't find the Sidebar item in Business or Jira Service Management projects.
Additionally, you need "Edit Issues" permission in the project in order to use the story mapping features.
You can rename the epic issue type in Jira.
If you do, Story Mapping app will ask you for the epic type once. In the free version, there is no feature to change this later. But if you absolutely need to, you can look at the Projects Entity Properties (you can install the Entity Property Tool to do this) - then change the "tech.realigned.project.stmEpicId" property to the new value.
Note that a feature to use arbitrary issue types as epics is included in the Pro version. The free edition only works with the default epic issue type of Jira.