Create
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Products
See all
Community resources
Top groups
Explore all groups
Community resources
Learn
Community resources
Events
Community resources

Issue rejection workflow

Mehmet Perk
Mehmet Perk
Contributor
October 28, 2019

I worked in around 10 different teams so far and the development workflow was usually similar, except the part where the person who accepts the user story rejects (not-accepts) it. What are the best practices here? How we currently do is the following:

  1. User story lands to the 'user acceptance test' column.
  2. The product manager reviews the story and goes through the acceptance criteria 1 by 1.
  3. PM writes a comment with each criterion's status (X or ✓) and moves the issue back to To Do
  4. Engineering lead checks the comment and aligns with the engineering team to re-create new sub-tasks.

I have a feeling that this is not so optimal and would like to hear your opinion. How is your 'rejection workflow?'

Comment
Watch
Like Be the first to like this
899 views

0 comments

Comment

Log in or Sign up to comment

Recommended Learning For You

Level up your skills with Atlassian learning

Learning Path

Jira Administrator

Jira Software

Configure Jira Software, Jira Core, or Jira Service Management, including global settings, permissions, and schemes.

12.7h Advanced
Path

Managing Jira Projects Cloud

Jira Software

Learn to create and configure company-managed projects in Jira Software and partner effectively with Jira Admins.

4h Intermediate
On Demand

Learning Path

Become an effective Jira Software Project Admin

Jira Software

This learning path is designed for team leaders who configure Jira Software projects to match a team's processes.

Intermediate
Free
groups-icon
Jira Cloud Admins
TAGS
AUG Leaders

Atlassian Community Events

    See all events