Hi!
Check out the plugin Scrum Assistant !
He can currently check 2 conditions:

• Do all the issue contain estimates in story points at the start of the sprint.
• Does the issue that is added to the active sprint contain an estimate.  

In the future, the composition of the parameters to be checked will be expanded.

It's time to try while the add-on is free.

I would say that this feature is a basic feature. A "must-have" feature if you want to create a scrum process management tool for real life. Is JIRA still in the same ridiculous decision as in sept-2013? I guess we (a big number of JIRA users) are just asking for basic features.

Wow, what a dismissive and frustrating answer.

This would be a very useful tool that our company would utilize as well.

I'm very sad that they closed this ticket without even considering adding it to their backlog.

This is the customer service equivalent of say, "No, that's stupid.  Go away."

Disappointed.

Hi Jira Agile Team,
We also have the same requirement, "to be able to check fixVersion field for all issues when a sprint starts"

is there any plan to implement firing of an event at the time of Sprint Start.

Thanks

Many thanks for reporting this issue, however this is not something we are going to add to JIRA Agile at this time.

Regards,
JIRA Agile Team

Current workflows are based around the status field and creation.

However, when using Jira Agile some important phases in the lifecycle of a story are introduced which are independent of status:

• when a story is added to a sprint
• when the sprint is started
• when the sprint is closed
• when the story is removed from a sprint

During all these actions it is useful to be able to validate the content of fields and/or to do post-operation actions following the action.

Some short examples:

• You may not want a story to be able to be added to a sprint unless it is in a particular state or a particular field has a particular value (e.g. Reviewed) or it is linked to an Epic that is in the same FixVersion or that it has an assignee
• When a sprint is closed you may want to update fields on some of the stories that are not yet complete (e.g. increment the count of times a story has not been completed on time, assign them to someone automatically for review, flag them as recently put on the backlog from a closed sprint)
• When the sprint is attempted to be started you could check that the stories in the sprint are all linked to Epics, have assignees, have story points, etc. before allowing the start to go ahead.