Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Start in the ticket, then go to Jira in the lower-right to make sure the two tickets are connected.

...

Available Fields

...

  • Project: Always “Shelter Buddy (SB)”

  • Issue Type - Options

    • Bug - An expected function of the software isn’t performing as it should, and it’s clearly something that both we and the customer expected to provide for them as part of our service.

    • New Feature - Feature request for functionality that does not yet exist but would benefit the customer. Please note, for 99% of these, they should follow the Known Non-Solutions procedure and not interfere with the devs regular activity (aka, try not to use this)

    • Task - This is an expected function of the software that can only be done by internal Pet Loyalty staff. (example: Kennel card customizations)

    • Improvement - Request for improved functionality based on existing features that would benefit the customer. Please note, for 99% of these, they should follow the Known Non-Solutions procedure and not interfere with the devs regular activity (aka, try not to use this)

  • Summary (This is a Title): “[Shelter Name] - [Summary, <8 words]”

  • Description - detailed description. Include items like URL to the page where the problem is going wrong, steps to reproduce the problem.

  • Reporter - who is submitting the ticket. Put your name here unless submitting on behalf of another PL employee. Be advised that if a non-CS rep is the reporter, then dev may not recognize the request as having come from CS.

  • Attachments (file upload) - Screenshots or other data where necessary.

  • Sync Notes and Comments - Yes. This helps devs get context about the ticket.

Fields Commonly Used

Next, click on Jira Ticket attached to the ticket to complete the submission

...