Closed chadwhitacre closed 8 years ago
Open | Closed | Queue | Description |
---|---|---|---|
0 | 23 | Violations | private communication amongst the safety team |
9 | 10 | Security | private communication with security researchers |
5 | 25 | Legal | private communication with our counsel |
6 | 860 | Support | private communication with users |
1 | 1 | L2 Support | escalated support issues |
4 | 39 | Team Review | public review of applications for new teams |
115 | ? | Errors | production errors |
0 | 1,635 | Vendors, etc. | private communication with our vendors (also includes low-volume mailboxes: safety and security) |
14 | 0 | Refund Announcement | a milestone |
7 | 98 | Pivot | a milestone |
14 | 38 | Balanced Shutdown | a milestone |
10 | 6 | Milestones | all milestones |
6 | 480 | PR Review | work in the final stage before deployment |
26 | 1,617 | PRs | all work in progress |
752 | 4,321 | Issues | public communication with contributors |
I hived off a new Refund Announcement milestone from the Pivot. Refund blog post needs to go up tomorrow night (September 1), with email blast on Wednesday.
I've trimmed up Refund Announcement. Gonna dive in on cleaning up the stats page ...
:swimmer:
Okay! Stats PR is ready for review. Screenshot at https://github.com/gratipay/gratipay.com/pull/3730#issuecomment-136436763. I'm gonna grab some lunch and coffee and then look at sprucing up the Team explorer: https://github.com/gratipay/gratipay.com/issues/3704. That'll take care of all of the Cached Values work we need before the 1.0 announcement.
After that I'll look at the Team Workflow issues. Once the workflow is nicer we'll open the floodgates and get that 1.0 refund announcement out the door!
Alright, Team explorer! https://github.com/gratipay/gratipay.com/issues/3704
Inbox 0, GitHub 0, L2 Support 0, Vendors, etc. 0.
Alright, Team explorer! https://github.com/gratipay/gratipay.com/issues/3704
:-)
@rohitpaulk What's your schedule like? You heading back to school here? Think you'll be able to start contributing again? :-)
Bla-friggin'-am.
I am having a new experience. I flip through windows and when I briefly hit Chrome, I think, "Damn, that's a classy-looking website." And then I realize it's Gratipay! :dancer:
I think we look better than we've every looked. Do you?
Alright. I'm done for the night. I made it through the Cached Value tickets for Refund Announcement, and started in on Team Workflow with #3484.
... that's https://github.com/gratipay/gratipay.com/pull/3484.
There are five tickets left on Refund Announcement. One is trivial (adding the "Apply" button to the homepage Team explorer), but we do also have to finish revising the blog post over on https://github.com/gratipay/gratipay.com/issues/3539. The biggest chunk of work I'd really like to get done before the announcement is https://github.com/gratipay/gratipay.com/pull/3568 ... and also https://github.com/gratipay/gratipay.com/issues/3743. So that's six tickets left. Good night. :-)
:moon:
Alright, tonight's the night to get this blog post up about the 1.0 refund. Gonna dive in here probably in an hour or two ...
Okay! Trying something new: posted up at the bar tonight. Open late! :) :beers:
Inbox 5, GitHub 0, L2 Support 0, Vendors, etc. 0.
Alright! What's next? Team review! https://github.com/gratipay/gratipay.com/pull/3568
:swimmer:
Actually, I'm gonna work on the blog post, under https://github.com/gratipay/gratipay.com/issues/3539. That's the thing that absolutely has to get up tonight. We can make more changes to the site in the coming days once the post is up.
Closed the Refund Announcement milestone. Gonna go sleep and take stock tomorrow.
!m @mattbk !m *
I think it's a big, big
this week!
:-)
Thanks, @mattbk. :-)
You ready for a communications and support push? We want to pay out as many people as possible before October!
Trying to catch up with all that have transpired since I have been missing
I may have noticed this before, but it's fun to (re)discover: Matz is on Gratipay! :-)
@mattbk Let's use the L2
tag instead of assigning to me. I almost missed https://gratipay.freshdesk.com/helpdesk/tickets/1733.
I've gone back through and tagged all closed tickets that were assigned to me as L2
, so if they're reopened they'll show up in the L2 queue. Unfortunately they also show up in the Support queue, so I've emailed Freshdesk support:
To: support@freshdesk.com Subject: a couple questions
1) I would like to make a ticket view that excludes a certain tag. Can I do that?
2) I would like to bulk-modify tickets to remove all assignments. Can I do that?
Thanks! :-)
Let's use the L2 tag instead of assigning to me.
Got it. For now I'll check the tag of any issue I open before responding, although most of the ones I send to you are familiar.
@mattbk Cool, thank you. It's fine if you want to respond to any reopened L2 (formerly assigned to me). I just missed FD2750 and FD1733, which I think you maybe thought were on my radar? Here's the view I check every day:
https://gratipay.freshdesk.com/helpdesk/tickets/view/1000241179
The point being that if a ticket is not on here, then I'm not seeing it:
https://gratipay.freshdesk.com/helpdesk/tickets/view/1000241179
I've added a note about escalating via L2
to:
Okay!
Inbox 4, GitHub 0, L2 0, Vendors 0.
Thanks for writing to Freshdesk today. I hope you are doing fine.
Let me come to your queries one by one.
- To create a custom view, I would request you to apply the tags on the filters on the Tickets view page excluding that one particular tag. Once that is done, you can follow the instructions in the screenshots that will help you create a custom view.
- Coming to your second query, kindly apply all the filters and view the necessary tickets. Once that is done, select all the tickets and use the Bulk Actions option to perform the actions on the selected tickets
I hope this helps Chad. Please do let me know if there is anything else that I can help you with. I'll be glad to help you out.
Thanks [].
I would request you to apply the tags on the filters on the Tickets view page excluding that one particular tag.
That's not what I want. I want to show all tickets that do not have a particular tag. Given these tickets and tags:
Ticket 1 [A] [B] Ticket 2 [A] Ticket 3
I want a filter that returns tickets 2 and 3. How do I do that?
[S]elect all the tickets and use the Bulk Actions option to perform the actions[.]
I don't see an option to bulk-remove assignments, only to bulk-add them. Is it there and I'm missing it?
Google results for the new design look not too bad:
Thanks for getting back to me.
- Currently our search is based on the OR rule. That is, we throw out results based on Tag A or Tag B and not Tag A and Tag B. So I'm afraid it wouldn't possible to have a search that excludes a particular tag.
- Getting to your second query, could you please let me know of your use case here? May I know as to know why you are looking to have the tickets unassigned?
Looking forward to your reply.
We don't use assignments in our workflow, so we would like to remove the assignments we currently have. In general it doesn't seem possible to bulk-remove anything (e.g., tags).
I'm really sorry that as of now, we do not have the option to bulk un-assign tickets.
I shall have this raised as a feature request to the Product Management team and shall get back to you once I get a word from them.
I'm sorry I couldn't be of much help here. Please do let me know if there is anything else that I can help you with. I hope you understand.
No worries, []. Thanks for your help! :-)
I really want to get the 1.0-payout form out tonight if I can: https://github.com/gratipay/gratipay.com/pull/3744.
I'm knocked out tomorrow w/ consulting, and then we're into Labor Day weekend.
What are you working on this week and why?
last week