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


I am new to Jira. just started working to set up two projects in Jira. First one is the agile and second one is for the project to be run in water fall model.

Any guidance or tips for Jira project setup is welcome.




Here's my advice...

  1. When creating new schemes try to only create them if you absolutely have to. Try to make workflows that are usable by a lot (nearly all) projects rather than a one-off for just your one project.
  2. This not only helps with administration but also helps your users gain trust and familiarity within JIRA. If they're going from project to project and seeing a completely different workflow for roughly the same kind of work, this doesn't bode well for the end-user's understanding of JIRA.
  3. Try to keep custom field creation to a minimum. The more custom fields there are, the less performance you'll see in JIRA.
  4. When designing a new workflow, keep it generic! If you have a workflow with too many statuses, users tend to get confused. There are always exceptions, however. Instead of creating more statuses, create more issues centered on that particular action. For instance, rather than create a "Review" status, create a JIRA issue whose summary is "Review" and use the same (or similar) workflow for that issue as the other issue types in your project.

Why are you running your projects using different methodologies? Are you just testing Jira out or are these real projects? 


Log in or Sign up to comment

Atlassian Community Events