Issue mapping to active sprint

[Shantanu Neema]

I am a new user having horrible experience with Jira. I created an issue, a simple task of moving the ticket to active sprint seems too complex, neither I can delete the issue and create a new one. I checked some other ticket where sprint is mentioned, in my ticket it says name of my team instead of sprint. 

[Trudy Claspill · Accepted solution]

Hello @Shantanu Neema 

Welcome to the community.

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.

At the top of the navigation pane, below the project name, it will also say the type of project - Business, Software, or Service Management. Which do you see?

Have you reviewed any of the "getting started" documentation or videos to gain a baseline understanding of Jira functionality?

Depending on the type of project with which you are working, the guidance for steps to add issues to sprints will vary.

With regard to deleting issues, Jira administrators often deny the ability to delete issues because once deleted the issue is permanently gone and cannot be recovered. If something is deleted in error there is no way to get it back. 

[Trudy Claspill]

Hello @Shantanu Neema 

The images you posted do not answer my questions. I need answers to my questions to provide you with meaningful guidance.

The discrepancy in the screen could be because the Sprint field is not available to the issues in your project, or it may not be displayed simply because it is currently empty and hidden when empty. Solving that is a separate issue from "how to add an issue to a sprint".

We need information about the type of project you are working with to provide guidance.

[Shantanu Neema]

I am in company managed project. I see 'Software Project' on top. I have not reviewed documentation videos. The thing is how come other member's ticket and my ticket have differences?. 

ability to delete anything created by mistake and recovering things after deletion is very normal requirement, I am no one to comment on that. 

[Shantanu Neema]

Is it something to do with access level available to me vs other members?

[Trudy Claspill]

Are the issues in the same project? Or are you working with a different project.

Normally issues are added to Sprints via the Scrum Board Backlog screen. Has a Scrum Board been created for this project, and are you able to access that Scrum Board?

Besides adding an issue to a sprint on the Scrum Board Backlog Screen, it is possible to add an issue to a sprint by directly editing the Sprint field for the issue. In your case, it is possible that the Sprint field is not shown because it is empty. Try clicking on the More Fields section to see if that reveals the field.

If it is automatically hidden when empty, you can click on the Configure option and change that by dragging the Sprint field from the Hide When Empty section to the Context Fields section.

[Shantanu Neema]

I think it all comes down to access level I have in our project. I do have a team level access and not at the project level which is preventing me to assign name of sprint in the ticket. 

I believe a sprint board exist and I can access that with no issues. Let me know if my understanding about access level is correct?

[Trudy Claspill]

Are you able to at least see the Sprint field when viewing the issue and expanding the More Fields section? Or do you see it listed in the Configure screen?

In Company Managed projects permissions are based on Permissions Schemes. A Permission Scheme determines if a user can see, create, update, and delete issues in a project, as well as more fine-grained permissions.

Jira Administrators manage the permission schemes and set which scheme is associated to a project. A Project Administrator can view the details of the Permission Scheme assigned to their project, but not modify the scheme.

Additionally, the fields that are available to each issue type are managed through Field and Screen configurations. These are also managed by Jira Administrators, and visible to Project Administrators.

These schemes can be different for different projects. And fields/screens can be different for different issue types in a single project.

Generally if you have permission to see the issue, then you have permission to see all the fields available to that type of issue. And if you have permission to edit any of the fields in an issue, you will have permission to edit the Sprint field.

If you are not able to see the field, I recommend you contact the Project Administrator for the project or the Jira Administrators for your instance to get additional assistance. It would take examination of the Field and Screen schemes and the Permissions scheme to determine why you can't see the field in the specific issue in the specific project you are viewing. And that info would not be available to people outside of your Jira instance (like the members of this user community).

[Shantanu Neema]

@Trudy Claspill Thank you for taking time to explain this. I learned something very critical about permissions from your response. I am seeing "None" under sprint field, that is the reason and it has to do with permission I have. 

[Trudy Claspill]

@Shantanu Neema 

That is not correct.

If you see "None" in the Sprint field, that only means it has never been assigned to a sprint. That does not mean you don't have permissions to add it to a sprint.

If you click in that field, where "None" is currently shown, you should be able to edit the field and select a sprint to which it should be added.

Note, though, that when you do this you will see ALL sprints that have been created in your Jira instance, not just the ones associated with Scrum Boards that concern your project. To avoid selecting the wrong sprint it is better to go to the Scrum Board for your project, go to the Backlog screen, and drag the issue from the Backlog section of the list to the applicable Sprint section shown above the list.

[Shantanu Neema]

The "None" under sprint field in above is not editable. 

[Nic Brough -Adaptavist-]

Could you tell us what type of project you are working in here?  In most views of the project, the left-hand side panel will say "team managed" or "company managed"

(There's a couple of ways of setting up projects to get this "sprint = none, and uneditable" behaviour, but I don't want to waste a load of time explaining the wrong one!)

[Trudy Claspill]

@Nic Brough -Adaptavist-  in one of the above responses Shantanu said the project is Company Managed and Software.

[Nic Brough -Adaptavist-]

Sorry, there's a lot here and I missed that bit!  Thank you!

So, if you can't set sprint, then there's either none that could contain the issue, or you don't have permission to set the sprint.  I can't think of another way to block that field in company-managed projects.

[Shantanu Neema]

@Nic Brough -Adaptavist- I think that is what it is. I confirmed with a colleague about the permission to set the sprint, it is not available for me.

[Nic Brough -Adaptavist-]

Check the permission scheme for the project the issue is in - do you have Edit and Schedule issue permission?

[Shantanu Neema]

I want something like on right, a name of sprint. I see Team in my ticket (left)