Cannot set issue types for Agility project

[Isaac Chua]

I have two Jira Cloud instances, one setup 2 years ago and one setup a week ago. The newer instance allows me to configure issue types on an Agility project. The older instance does have that option (and other options like Reports are not available either). How can I turn on that option?

[Jack Brickey · Accepted solution]

@Isaac Chua, per your request I have broken out my comments here to convey the ultimate cause of the issue you experienced.

The reason why one of your instances allows you to access Issue Types and the other does not is that Atlassian is rolling out Agility updates continually. Your instances are on two different version. Getting them on the same version requires contacting Atlassian Support.

[Isaac Chua]

Thanks @Jack Brickey.

[Julien Femia]

@Isaac Chua @Alexey Bogdanov The new Jira experience is being rolled out in different phases to our customers. This is the main reason why you might be seeing different things between your instances.

It is is beta and has all sorts of issues IMO.

@Jack Brickey Can I ask you to elaborate on that? What are some of the issues that you're currently experiencing with Agility projects? We are constantly rolling out improvements to this new experience and feedback is always very helpful.

[Jack Brickey]

@Julien Femia, my comment is based off partly on my own experience as well as that of others I have come across here in the Community. I have provided some feedback to another Atlassian in an earlier thread. Here are a couple of points:

• let me preference that I do not actively use Agility projects. I’m really not sure what their strength is over other SW projects with kanban or scrum
• i have two test project and they don’t behave the same. Example, an older one I created for test purposes does not have issue types or rules. Another has rules but only one rule
• they seem overly simplified for my taste. I prefer to be able to configure filter, columns, quick filte4s, cards, etc.
• do they have a planning board/backlog. I’m unsure at the moment. Important to me 

[Julien Femia]

Thanks a lot for the feedback, my answers below

I’m really not sure what their strength is over other SW projects with kanban or scrum

The real power of agility boards is that teams can add / remove features to the board as they go. It allows them to adjust any aspect of their style of work in seconds. You can read a bit more about the rationale behind agility in this blogpost.

We're also completely re-imagining the project configuration experience, and opening the creation of project to anyone. You can read more about it in this blogpost.

I have two test project and they don’t behave the same. Example, an older one I created for test purposes does not have issue types or rules. Another has rules but only one rule

As I said in my answer above, we're releasing those features progressively, so you should start seeing the same features as time goes. There is only one type of rule for now, but we'll start releasing a second type soon, and you can expect a third and fourth one to follow. Stay tuned!

they seem overly simplified for my taste. I prefer to be able to configure filter, columns, quick filte4s, cards, etc.

We understand that agility projects are still missing some of the more powerful features of the old templates, but we're actively working on them to make sure that this power is there. Regarding columns, you can change your workflow and create/rename/delete columns inline from the board directly.

do they have a planning board/backlog. I’m unsure at the moment. Important to me 

Yes they have! :) You can enable the backlog view by going to your project settings, and accessing the "Features" menu.

Let me know if there is anything else that I can do to help!

[Isaac Chua]

@Julien Femia I understand if Atlassian is releasing features progressively, but why is the experience not the same across the board? For instance, why am I not able to set issue types in one instance whereas I can on another?

Also, I can't seem to release issues from the board the same way I can on Kanban.

[Jack Brickey]

@Isaac Chua, the answer depends on what you mean by “instance. The two possibilities are below.

two physical Jira installations - the actual sowftware is different. Atlassian doesn’t update all instances at the same time.

one instance but two projects - one project was setup under version version A and later a new project was setup under version B. The projects will assume the behaviors of the then current SW.

[Isaac Chua]

@Jack Brickey instance in the sense of two separate Atlassian Jira Cloud URLs. I would like to put up a request to upgrade my older one to the latest. Is that possible?

[Jack Brickey]

you would need to reach out to Atlassian Support to request that.

[Julien Femia]

@Isaac Chua what Jack said, feel free to reach out to our support teams and they'll be able to update your instance.

Also, I can't seem to release issues from the board the same way I can on Kanban.

Resolved issues are currently automatically removed from the board after 14 days on agility projects. You're not the first one to provide us that feedback, so we'll soon start some work to enable a more manual way of clearing the board. Stay tuned :)

[Isaac Chua]

@Jack Brickey thanks, I have gotten Support to turn that on. It'd be good if you could put your reply as a separate answer so it could be marked as the right one.

That said, there is something strange since I'm getting part of it in Spanish:

@Julien Femia Got it. It would be good if a similar behaviour to Kanban is available, which lets us set the release version upon releasing the issues.

[Isaac Chua]

The support staff has created the bug report: https://jira.atlassian.com/browse/JRACLOUD-69902

[Isaac Chua]

@Julien Femia I just noticed the fields for Affected Version and Release Version are not available on the Agility Board as well. Please make those available together with the release issues feature.

[Alexey Matveev]

Hello,

Agitlity project is a new type of projects in Cloud. It is an independent project. Configuration of this project type is very limited. But the advantage of this project type is that any user without the Administrator permission can create such project. You can revoke permission to create independent projects in the Global permission scheme. You can find more info about independent projects here:

https://confluence.atlassian.com/jirasoftwarecloud/managing-independent-projects-942834582.html

[Alexey Bogdanov]

As I understood the problem is that different Jira Cloud instances have different feature set for Agility projects.

We faced the same problem. I created an Agility project in existing account and some of the features are not available there. For example, Reporting and Issues types.

Why?

[Alexey Matveev]

All Jira Cloud  instances have same features. Agility project exists in every Cloud instance. Agility project does not equal to a Software project. It is an independent project.

[Alexey Bogdanov]

Sure. I've created Agility project.

Why there is no Issue types section in Settings?

[Alexey Bogdanov]

And also:

[Alexey Matveev]

Are you a Jira administrator?

[Alexey Bogdanov]

Yes.

[Jack Brickey]

This is one of the reasons I don't (yet) use Agility. It is is beta and has all sorts of issues IMO.

I have two Agility test projects. The left one was created ~6wks ago and Agility2 created last week. Agility2 allows me to add Issue types.

[Isaac Chua]

I was going to reply exactly as Jack Brickley did. The first picture is what I see in my older instance I had started 2 years ago. The second picture is what I see in my newer instance started 2 weeks ago. Where are the issue types for my project?