Skip to main content

1/23/19 Rollup

Product Updates​

  • New beautiful pricing table!

  • Checkout is now ONE CLICK! End wobblies won't see the confirm button when trying to pay through PP Button / Form Builder / eCommerce

IT'S DEAD

Bug List​

  • Full List: https://powr-support.zendesk.com/agent/filters/188908428
  • Keep an eye out for bugs related to the Pricing Table update mentioned above. Issues would likely be related to upgrading plugins.
  • The majority of Smart Button payment related bugs have been squashed. There are a few smaller edge cases that have popped up, but those are fewer and further between.

JIRA Guide​

All Tier 1 agents now have access to JIRA! This is where agents can easily view the status of a bug. The access to JIRA is in LastPass, and you can log in here: https://powrtrak.atlassian.net/

JIRA looks like this (quite similar to Trello)

Support can have trouble understanding the current status of a bug, since things move so quickly at POWr. Your JIRA access is a clear way to see what our engineers are working on, and it's also a way to keep track of issues with multiple tickets without needing to create Problem Tickets. That's a mouthful. Let's see what it looks in action.

You're crushing tickets in the inbox, and you come across a valid issue. Let's use this bug as an example.

You go ahead and verify that this is in fact a bug, and that the little trash can in the Form Response Dashboard doesn't actually delete responses. Now, you'd go and take a look at JIRA.

Aha! There's a card for that issue, and it's in the To Do list. So you'd take note of the card number, which is PM -5399.

You'd go back to the ticket, scroll down on the Apps list, and click Link Issue:

You can search by JIRA card number, or by JIRA card title. Once you find that card, just select it and click Link Issue at the bottom.

It'll look like this:

Then, you just have to reply to the user and say the engineering team is on it. You can set the assignee to Ben and set it to On Hold, and then you're done.

This should significantly cut down the time that you spend on debugging tickets. Ben and I create JIRA cards for the issues 3 times a week, so there might be times when there aren't cards created yet. But, when there is a card for an issue, you just have to link it. No need for a lengthy internal note, since the issue has been identified/reproduced already.

Going forward, make sure to cross reference anything you would escalate to Engineering with the JIRA board. If there is a card, you just need to link it and put it in the Engineering folder. If you come across an issue that does not have a card, you'll have to create an internal note (the original way) so Ben and I can create a JIRA card.

I'm also working on creating a Slack channel that simply lists all current bugs with JIRA cards, but that's still in the works.