Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

JIRA Cloud Issue Types

Hi All,


I have two comments on the JIRA cloud version vs JIRA on-prem.

  1. The Issue type default values are Epics, User Story and Tasks. Feature is a missing issue type. Though it's a mostly an optional issue type and not pre-dominantly used across projects, it is a good to have feature without waiting on the JIRA admins to configure the JIRA board
  2. The option to collapse the Story read view on the right side of the user story in a sprint should be collapsible to give a longer view to read the associated User Story details 


I am not sure what you are asking about here.  Two different pieces of software do things a bit differently to each other.

Like # people like this

I agree. I wanted to provide the feedback as an end-user of the application to help improve it get better with stack available for customization. 

Ok, well, on point 1, you can add Features if you want to, it's up to you.  On point 2, use the other view, then you don't need to collapse anything.

Interesting comments @Amit Vashishtha but like @Nic Brough -Adaptavist-  I am unsure if you are just wanting to make a statement or wanting to provide feedback or needing support.

Like # people like this

It was a constructive feedback as an end-user for improvement of the application. I saw noticeable differences on the Cloud version which limit my ability to fully utilize the application as per needs. Having an additional set of clicks to finally reach the bigger view or create hierarchy is a trade-off per my opinion for a cleaner UI. I will prefer functionality over interface.


Log in or Sign up to comment

Atlassian Community Events