Nic Brough's explanation: https://answers.atlassian.com/questions/68597/on-the-usage-of-jira-workflow-status-and-steps
Maybe this will help before someone will give you detailed explanation:
A step represents a workflow's current status for an issue. An issue can exist in one step only at any point in time. Each workflow step corresponds to a linked status . When an issue is moved into a particular step, its status field is updated to the value of the step's linked status.
Although steps and statuses are treated separately when administering workflows, they are effectively synonymous concepts in JIRA and as such, it usually helps to name a step after its linked status (source https://confluence.atlassian.com/display/JIRA050/Configuring+Workflow)
Step is a part of workflow and status is a part of issue. Just that!. You need to map each step of your workflow with one status and there are 1:1 relationship between them. Transitions is a bridge that link to steps with each other for movineg issues from one step to another. If you new to jira I suggest this book for you for start administrating it:
I’m a designer on the Jira team. For a long time, I’ve fielded questions from other designers about how they should be using Jira Software with their design team. I’ve also heard feedback from other ...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs