forked from paviliondev/discourse-tickets
-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
How do discourse-solved and discourse-assign store their information? #10
Comments
willmurphyscode
added
general-question-and-other
ready-for-pairing
and removed
backlog
labels
Jun 8, 2018
h-m-m
added
in progress
ready-for-pairing
and removed
ready-for-pairing
in progress
labels
Jun 8, 2018
At least for now, we are not using Discourse Solved. |
freestylebit
added a commit
that referenced
this issue
Jun 10, 2018
# This is the 1st commit message: Render alpha version of create ticket widget Add a button to the interface that allows the user to convert a topic to a ticket and change its tags. Co-authored-by: Howard Miller <howard.m.miller@gmail.com> Co-authored-by: Jen Pengelly <jgpengelly@gmail.com> Co-authored-by: Exbinary <exbinary@gmail.com> # The commit message #2 will be skipped: # move topic tagging button # The commit message #3 will be skipped: # make the topic ticketing button do *something* # The commit message #4 will be skipped: # asdf # The commit message #5 will be skipped: # add populated reasons dropdown # The commit message #6 will be skipped: # add populated status dropdown # The commit message #7 will be skipped: # Experimental # The commit message #8 will be skipped: # Ajax # The commit message #9 will be skipped: # Move # The commit message #10 will be skipped: # Remove unnecessary items # The commit message #11 will be skipped: # move to component # The commit message #12 will be skipped: # Lint # The commit message #13 will be skipped: # Move things around # The commit message #14 will be skipped: # DRY further # The commit message #15 will be skipped: # Simple # The commit message #16 will be skipped: # asdf # The commit message #17 will be skipped: # asdf # The commit message #18 will be skipped: # Removed unused i18n key # The commit message #19 will be skipped: # asdf
freestylebit
added a commit
that referenced
this issue
Jun 10, 2018
# This is the 1st commit message: Render alpha version of create ticket widget Add a button to the interface that allows the user to convert a topic to a ticket and change its tags. Co-authored-by: Howard Miller <howard.m.miller@gmail.com> Co-authored-by: Jen Pengelly <jgpengelly@gmail.com> Co-authored-by: Exbinary <exbinary@gmail.com> # The commit message #2 will be skipped: # move topic tagging button # The commit message #3 will be skipped: # make the topic ticketing button do *something* # The commit message #4 will be skipped: # asdf # The commit message #5 will be skipped: # add populated reasons dropdown # The commit message #6 will be skipped: # add populated status dropdown # The commit message #7 will be skipped: # Experimental # The commit message #8 will be skipped: # Ajax # The commit message #9 will be skipped: # Move # The commit message #10 will be skipped: # Remove unnecessary items # The commit message #11 will be skipped: # move to component # The commit message #12 will be skipped: # Lint # The commit message #13 will be skipped: # Move things around # The commit message #14 will be skipped: # DRY further # The commit message #15 will be skipped: # Simple # The commit message #16 will be skipped: # asdf # The commit message #17 will be skipped: # asdf # The commit message #18 will be skipped: # Removed unused i18n key # The commit message #19 will be skipped: # asdf
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Specifically, how would we call their code to assign or solve something?
The text was updated successfully, but these errors were encountered: