Skip to content

Instantly share code, notes, and snippets.

@ninapavlich
Last active September 27, 2019 21:50
  • Star 0 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
Star You must be signed in to star a gist
Save ninapavlich/fd5ba7acc071a84e329dc5b87ba545c5 to your computer and use it in GitHub Desktop.
JIRA Create Bug and Story Bookmarklets
javascript: (async function() {
/* Bug template created by Anna Smith, Program Manager at NYTimes */
const summaryTemplate =
"**Bug Ticket Template** EPIC | Bug : [High-level summary]";
const descriptionTemplate = `*Howdy! This is the bug ticket template. Please copy and paste this when you create a new ticket.* To get started, go to the "Configure Fields" dropdown in the upper right of the Create Issue pop-up screen. Select only the following: Assignee, Attachment, Description, Epic Link, Priority, and Sprint. (You'll only need to do this once.)\n\n\n\n
 
*ISSUE TYPE*\n
* Select "Bug" from the dropdown menu (versus Story, our default). \n\n\n\n
 
*TICKET TITLE*\n\n
EPIC | Bug: [High-level summary]\n
* Epic: What project is this ticket a part of?\n
* High-Level Summary: succinct summary of the work to be done\n\n\n\n
 
{color:#00875a}*DESCRIPTION FIELD (THIS AREA!)*{color}\n\n
{color:#00875a}_Summary_{color}\n
* {color:#00875a}High-level description of the bug{color}\n\n
{color:#00875a}_Actual Behavior:_{color}\n
* {color:#00875a}Describe what's currently happening.{color}\n\n
{color:#00875a}_Expected Behavior:_{color}\n
* {color:#00875a}Describe what should happen, when this feature is working as expected.{color}\n\n
{color:#00875a}_Found on:_{color}\n
* {color:#00875a}Operating system and version:{color}\n
* {color:#00875a}Device and version:{color}\n
* {color:#00875a}Browser type and version:{color}\n\n
{color:#00875a}_Steps to Reproduce:_{color}\n
* {color:#00875a}How can another user duplicate the problem you're seeing?{color}\n\n\n\n
 
*OTHER FIELDS*\n\n
*Epic Link:* Start typing in the name of the epic and the name the epic should appear in the dropdown. If no epic exists, create one.\n\n
*Priority:* Leave this as Medium (the default) _unless_ this ticket is blocked. In that case, select "Blocker" from the dropdown.\n\n
*Assignee:* If you already know who's tackling this, assign the ticket to them. If not, use one of the following aliases:\n\n
* Design: parenting-des\n
* Development: parenting-dev\n
* Product: parenting-prod\n\n
*Attachments:*\n
* Attach any relevant files (typically, screenshots).\n\n
*Sprint Link:*\n
* If you know what sprint this work will be a part of, start typing its name and the sprint should appear in the dropdown. If you don't know, skip this field. The ticket will automatically be added to the backlog.`;
const jiraBaseURL = "https://jira.nyt.net/";
const pid = "18174"; /* 18174 => Parenting Project */
const issueType = "1"; /* 1 => bug, 7 => story; */
const url = `${jiraBaseURL}/secure/CreateIssueDetails!init.jspa?pid=${pid}&issuetype=${issueType}&summary=${encodeURIComponent(
summaryTemplate
)}&description=${encodeURIComponent(descriptionTemplate)}`;
window.open(url, "_blank");
})();
javascript: (async function() {
/* Story template created by Anna Smith, Program Manager at NYTimes */
const summaryTemplate =
"**Story Ticket Template** EPIC | [Action] : [High-level summary]";
const descriptionTemplate = `*Howdy! This is the story ticket template. Please copy and paste this when you create a new ticket.* To get started, go to the "Configure Fields" dropdown in the upper right of the Create Issue pop-up screen. Select only the following: Assignee, Attachment, Description, Epic Link, Priority, and Sprint. (You'll only need to do this once.)\n\n\n\n
 
*TICKET TITLE*\n\n
EPIC | [Action] : [High-level summary]\n
* Epic: What project is this ticket a part of?\n
* Action: Create? Define? Design? Build?\n
* High-Level Summary: succinct summary of the work to be done\n\n\n\n
 
{color:#00875a}*DESCRIPTION FIELD (THIS AREA!)*{color}\n\n
{color:#00875a}_Summary_{color}\n
* {color:#00875a}User story and/or work to be done{color}\n\n
{color:#00875a}_Acceptance Criteria:_{color}\n
* {color:#00875a}How do we gauge if this work has been successfully completed?{color}\n
* {color:#00875a}Put another way, how do we know if the business / user needs have been met?{color}\n\n
{color:#00875a}_Artifacts_{color}\n
* {color:#00875a}_Typically design artifacts, but include links to other relevant documentation, as needed_{color}\n\n
{color:#00875a}_Analytics Requirements:_{color}\n
* {color:#00875a}Please consult with {color}[~209802]{color:#00875a} about what, if anything, needs to go here.{color}\n\n
{color:#00875a}_QA Testing Notes:_{color}\n
* {color:#00875a}What artifact to be tested? Where can it be found? {color}\n
* {color:#00875a}Is VQA required? Browser / functional?{color}\n
* {color:#00875a}Include any relevant testing instructions / caveats.{color}\n\n\n\n
 
*OTHER FIELDS*\n\n
*Epic Link:* Start typing in the name of the epic and the name the epic should appear in the dropdown. If no epic exists, create one.\n\n
*Priority:* Leave this as Medium (the default) _unless_ this ticket is blocked. In that case, select "Blocker" from the dropdown.\n\n
*Assignee:* If you already know who's tackling this, assign the ticket to them. If not, use one of the following aliases:\n
* Design: parenting-des\n
* Development: parenting-dev\n
* Product: parenting-prod\n\n
*Attachments:*\n
* Attach any relevant files (typically, screenshots).\n\n
*Sprint Link:*\n
* If you know what sprint this work will be a part of, start typing its name and the sprint should appear in the dropdown. If you don't know, skip this field. The ticket will automatically be added to the backlog.`;
const jiraBaseURL = "https://jira.nyt.net/";
const pid = "18174"; /* 18174 => Parenting Project */
const issueType = "7"; /* 1 => bug, 7 => story; */
const url = `${jiraBaseURL}/secure/CreateIssueDetails!init.jspa?pid=${pid}&issuetype=${issueType}&summary=${encodeURIComponent(
summaryTemplate
)}&description=${encodeURIComponent(descriptionTemplate)}`;
window.open(url, "_blank");
})();
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment