Only Commit to Item in Active Sprint

[awedekind]

There are some stories/bugs I've been able to commit to that are not in an active sprint. The only items that should be getting worked on are ones in an active sprint.

As a user I would like the hook to only let me commit against items in the current/active sprint.

[kthompson55]

When you make these commits, are you pushing against only the item individually, or are you pushing against multiple stories/bugs?

[awedekind]

I'm only committing against a single issue at a time.

[kthompson55]

After some deliberation of the people involved in the project, we have decided that, for the time being, that developers will be able to push against issues from previous sprints, but will a warning displayed that the issue they are committing to is from a previous sprint.

[mtscout6]

After even more deliberation is was determined that there may be cases where some devs work outside the sprint cycle. For example Corey, Bob, or Jeremy. In those cases there would not be a sprint for them to put their work in. So, we will opt to using a yellow text warning that said issue is not a part of an active sprint. Should that change then the work will have already been done and only minor tweaks would need to occur to change it to an error.

[kthompson55]

For this issue, we need to find a way to pull a JIRA sprint based on the id provided in the customfield_10804. Unfortunately, I do not have time left in this Enterprise Project to learn how to pull the sprints and collect the desired information.

Sorry.

[dportzline83]

There are also times when we work on stories that are coming up in the backlog, but we have not committed to them in the current sprint. We could enforce that they be dragged into the sprint if work is started on them, but some teams may prefer to only pull things in that they've committed to completing. This seems like a decision better left to each team.