We had discussed in the beginning that we would use something akin to the following issue creation strategy:
1) Create Epics for high-level concepts or efforts 2) Create a Story to represent a feature that supports an Epic and link it using isPartOf 3) Create Technical/Sub tasks on the story for the implementation details In addition to these categories, we of course have tasks (like releases or web page management) and bugs. Recently, I have seen a lot of issues get duplicated or created using a different pattern than the one we discussed. If no-one objects, I will change the website's link to JIRA so that it takes the visitor to the description of our JIRA management strategy before linking on to JIRA itself. Also, I think it would help if we made an explicit effort to look for similar existing issues before creating new ones; linking duplicates or related issues; and making sure to update the state of issues as they are worked. I have taken a first pass at linking duplicates, but probably missed a few. -Matt
