Skip to end of metadata
Go to start of metadata

Steps to follow to create a new Jira

  1. Create a new Jira by clicking on the Create button.
  2. Fill in the fields with a good description of the what the Jira is trying to achieve. It helps to add some information in certain cases about why the JIRA was create. What is the issue that caused this JIRA to be filed?
  3. The best way to capture the business relevance of the Jira is to word the Jira using the following format “ As a <ROLE> I want to be able to do <X> so that I can achieve <Y>." For example: As a <User> I want to be able to <reset my password> so that <I can get a new password in case I have forgotten it>.
  4. Include Acceptance Criteria.  For example, user can reset password in the device.
  5. If you know the possible assignee for the Jira, assign the person to it.
  6. Upload screenshots, descriptions, files, link to ACRA or any information that will help the developer to understand the requirements on the Jira.
  7. Project Owner will triage new ticket by asking for clarifications from requester and including relevant labels.  Once the ticket is clear and includes all the relevant information, Project Owner will change the status of the Jira to “Ready for Work”.



Steps to follow to take a Jira to completion.

  1. Assign the Jira to yourself.
  2. Change the status of the Jira to “In Progress”.
  3. If you find that you are unable to make progress or get started on a Jira as you are waiting on some information from the implementer/creator, the status should be changed to “Waiting on Information”. This situation may occur at any point in the Jira's life.
  4. Fill in the Estimated time fields.
  5. Make the required code changes as per the Jira’s requirements.
  6. If you find that you have questions, information to be shared please leave a comment on the Jira with the necessary information. Email/chats/scrum records are usually never recovered. So it’s best to leave as much information as possible on the JIRA page to make sure the ticket is well documented. This will be help anyone understand the reasoning and logic behind the solution to the Jira.
  7. Comments could also include screenshots in cases where there is a UI involved.
  8. Test your changes locally.
  9. Commit the code to Github.
  10. Issue a pull request.
  11. Update the Jira with a comment that includes the commit-id and the link to the Pull Request with the changes made.
  12. Change the status of the Jira to “Testing Needed” if snapshot of apk or snapshot of module is ready for testing.  If not, change status to “code review” so that Lead Developer can review and merge the code to the apk or module for testing (status will change to “Testing Needed”).
  • No labels