I have a brand-new instance of Jira Data Center that was installed this morning. I have Administrator privileges to the DC instance. I create a scrum software project and added myself as a Project Admin. I also made sure that all of the permission schemes were set up correctly.
I created a single issue in the project. This is what I have observed:
1. I re-indexed the new instance before starting.
2. The issue does not appear on the Backlog screen.
3. There is no "Create Sprint" button on the backlog screen.
I have been battling this problem for nearly a week and I have researched the Jira documentation, knowledge base and Atlassian Community thoroughly. Has anyone else ever seen this issue before? If so, what was the root cause and the fix?
Check your filter, It does not work if your pulling from multiple projects. It only works for a single project in your filter.
Thanks for posting your question on the community forums.
Initially, there might be the case you already have a started (and not completed yet) sprint.
If a new sprint is created, it cannot be started unless you enable the "Parallel Sprints" feature on the Jira Software -> "Applications" -> Jira Software configuration section, as shown in the capture below:
Ref. https://support.atlassian.com/jira-software-cloud/docs/use-parallel-sprints/
I hope this helps you and solves the problem.
- Pablo / SSE - ServiceRocket
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Pablo,
Thanks for the response. But as I mentioned in my post - this is the first project in this instance and since the "Create Sprint" button is not visible, there are no Sprints created. So, the situation that you described is simply not possible. But thanks for trying to help. This is just quite frustrating!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks for clarifying this. I might have misunderstood the initial description.
This is a really strange situation. The only basic way to reproduce the behavior or to prevent the creation of sprints is to modify the Manage Sprints permission.
I know you reviewed the permissions, but it could be worth double-checking using the Permission Helper to ensure the Manage Sprints permission is OK for the relevant Jira user.
The example below is for the test I've made. I hope this helps you in any way.
- Pablo
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Pablo,
We have figured out that the SSL certificate is causing the issue. Unfortunately, Atlassian does not support these types of problems so we have had to figure this out on our own. We are working towards a solution now.
Thanks for your response!
Tammy
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.