rubyforgood / discourse-ticketing Goto Github PK

Agenda for Friday morning:

1. Break into small groups (2, 3, 3), and read the threads:
   • https://community.namati.org/t/ruby-for-good/43213/14?u=lasitha
   • https://meta.discourse.org/t/using-discourse-as-ticket-system-so-no-balls-are-dropped-woman-juggling/82698?u=willmurphyscode
2. Small groups write up a shared understanding of what is in the thread
   • These groups try to break down the problem
   • Generate questions about what we will build and how
3. Come back together and check our shared understanding
4. Work on a backlog, and plan work for the day

• Introductions
• Quick update on progress
• Throwaway wireframes
  • Dashboard
  • Compose
• Questions:
  • Tags vs custom_fields
  • Rails engine?
  • Where does dashboard live?
  • Personas
  • Dependencies
  • Seeding?

Specifically, seeding all the tags and tag groups.

Specifically, how would we call their code to assign or solve something?

Acceptance Criteria:

There is a table that shows the title of every topic tagged ticket.

Including:

• Warn user if they are about to assign something that is not a ticket
• Others

https://meta.discourse.org/t/beginners-guide-to-creating-discourse-plugins-part-1/30515

Specifically, seeding tags and tag groups.

We should write a good question for Tobias about these groups overlap:

1. Admin
2. Moderator
3. Staff
4. People who can see and work on tickets.

My current assumption is that groups 3 and 4 are the same, and are the union of 1 and 2.