Description when a JIRA task has not been started

[JackGilliam1]

When committing to a JIRA task that has not had 'Begin Work' clicked (Not started). The description is too vague and could be improved explaining why the commit could not be made.
Currently it states:
Error: Cannot commit issue X because parent issue Y is not available to commit against.

Instead it could state:
Error: Cannot commit issue X because parent issue Y has not been started

[mtscout6]

The problem with that proposed terminology is that it is tightly coupled with the workflow that you are dealing with. Perhaps a better alternative would be:

Error: Cannot commit issue X because parent issue Y is not in a state that can be committed to, please check that issue's workflow and transition it to a committable state.

How does that sound?

/cc @RyanHauert @andhernand

[JackGilliam1]

How about we list possible solutions we could try, such as "the issue is started" or "the issue is not in a completed state" or both

[mtscout6]

Again tightly coupled with your specific use case. As we add more functionality to the commit hook this will only get trickier, thus my reasoning for a message that directs you to look at the workflow for the issue in question.