Entering TIckets in JIRA with more details

[jfuentes]

So I am running into an issue where people are entering backlog tickets with very little information.  And when creating a Sprint it is very difficult to do estimates with little information.  How do I enforce certain information during the creation of any ticket.  

Such as 

• Goals
• Strategic fit
• Acceptance Criteria

[Bill Sheboy · Accepted solution]

Hi @jfuentes -- Welcome to the Atlassian Community!

To me, this sounds more like a process issue than a tooling issue.

How does your team normally "intake" new work requests?  There may be a gap where the product owner/champion is not effectively communicating with stakeholders what is needed to evaluate requests.  Partnering with stakeholders to clarify requests helps them better understand the business problems they are trying to solve and the relative priority of requests.

You *could* certainly add custom fields and make them required in Jira for all new issues.  I have found doing that without supporting partnership leads to people just typing in filler to get past the edits.

Best regards,

Bill