3 ms·

Awesome work! I love how simple it is while still adding so much. I know you've mentioned this elsewhere, but I was a bit confused by the tickets. I get what t

Awesome work! I love how simple it is while still adding so much. I know you've mentioned this elsewhere, but I was a bit confused by the tickets. I get what they are, but who is the intended user? One feature I'd like to see is custom statuses. I personally am a big fan of "In progress -> Pending deploy -> Verify -> Done" instead of just "Done". It makes it really clear what just went out with every deploy, and allows the person who originally filed the issue to be the final arbiter on whether or not it was actually solved. Another cool things would be integrations! If you have a ticketing system, it would be great if that tied into the tools that the customer support teams use. I use intercom myself, and it'd be handy if I could create a ticket out of an intercom request and remember to follow up with that user after the fix is deployed.

jenniferDewalt 11y ago
Thanks! We created tickets with non-technical people in mind as way they could report bugs, feature requests and the like without cluttering up issues for developers. Since the tickets track the work on their linked issues, the ticket owner has a clear picture of what the progress is on their ticket. However, we've also seen dev teams hack tickets as a way to scope groups of issues together, for a feature release for example, similar to epics in Agile workflows. Would you like to see custom statuses on board, the tickets or both? We are really excited to add more integrations! Slack, ZenDesk and Intercom are some of the big ones we're looking at.
- jmtulloss 11y ago
  Oh I was thinking of the board, not tickets. But perhaps it's more relevant in tickets? I'm not sure, just an idea. Years ago I worked at a company that had a jira flow that worked with those stages for tickets and I thought it was great. Haven't been able to replicate that workflow since.
  - jenniferDewalt 11y ago
    Gotchya! We've been thinking about how to add some flexibility to the columns without falling into the 'endless column' trap where teams end up with dozens of micromanaged columns. It sounds like that level of organization would still fit the paradigm.

jenniferDewalt 11y ago

Thanks! We created tickets with non-technical people in mind as way they could report bugs, feature requests and the like without cluttering up issues for developers. Since the tickets track the work on their linked issues, the ticket owner has a clear picture of what the progress is on their ticket. However, we've also seen dev teams hack tickets as a way to scope groups of issues together, for a feature release for example, similar to epics in Agile workflows. Would you like to see custom statuses on board, the tickets or both? We are really excited to add more integrations! Slack, ZenDesk and Intercom are some of the big ones we're looking at.

jmtulloss 11y ago
Oh I was thinking of the board, not tickets. But perhaps it's more relevant in tickets? I'm not sure, just an idea. Years ago I worked at a company that had a jira flow that worked with those stages for tickets and I thought it was great. Haven't been able to replicate that workflow since.
- jenniferDewalt 11y ago
  Gotchya! We've been thinking about how to add some flexibility to the columns without falling into the 'endless column' trap where teams end up with dozens of micromanaged columns. It sounds like that level of organization would still fit the paradigm.