-
Notifications
You must be signed in to change notification settings - Fork 360
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
Update issue template to point to Jira #4995
Conversation
<!-- Are you seeing something that looks like a bug? Then great! You're in the right place. --> | ||
<!-- Are you seeing something that looks like a bug? Then great! You're almost in the right place. --> | ||
|
||
<!-- You'll want to go to https://broadworkbench.atlassian.net/projects/BA/issues and then tell us: --> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We should probably remove all this "remember to include" cruft while we're here. We can always make them JIRA fields instead
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Have a link?
Briefest of googling, I only found a way to do templates at ~$10 per Jira user.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🤢
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
QA has it set up for prod issues, so if they can do I'm guessing we can too
I think this is great! I would like @ruchim to take a look and see what she thinks about turning off issue creation after a certain date. Also, if we should close out all of the existing tickets after that date. Jira is open for folks to join and look at our board so this shouldn't be too big of a pain, but I don't know how we would get the message out to everyone. |
### | ||
### https://broadworkbench.atlassian.net/projects/BA/issues | ||
### | ||
### You may need to create an account before you can view/create issues. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
TOL: Should we add that they can use their Gmail account for the same purpose?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Oops, I missed this before merging. Could be a good follow up though (but is it true? I thought they could create an account using their gmail, but not sign in with it? Maybe my confusion is exactly why we should add something!)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You can sign in with any Google account, there is no user facing "account creation" sequence per se though obviously behind the scenes JIRA is registering you in its user database
No description provided.