...

In the case of one-off requests, if you find yourself creating tickets for a lot of data requests, it may make sense to create an Epic for it. You could also create an Epic for recurring administrative tasks for a service.

Before you create a Ticket (or an Epic), you should see if a relevant Epic already exists by looking here.
If you feel an Epic is needed that doesn’t exist, create one by clicking the Create button.

...

How do I tie a ticket to GitHub?

1. Create a ticketUse

2. Begin branch names with the ticket key (e.g. dsdw-588) as your branch name (lowercase is preferred). Also, lowercase is preferred). You can also add additional metadata such the branch owner and description, separated by dashes (e.g canvas-874-etsur-show-multiple-nonsis-users).

3. In pull requests, paste the URL to the ticket in a comment when you open a pull request, this makes it easy to link back to the ticket when reviewing a pull request.
   

   

4. The JIRA-GitHub integration should pick up all commits, pull requests and builds associated with the that branch.
   

   

5. If GitHub activity from your repo isn’t being reflected in your JIRA ticket, reach out to Rob Piscitello and work with him to get your repo added to the GitHub-JIRA integration.