Exploring the legal landscape: Jira ticket production

Staying informed of new decisions, developing case law, and evolving expectations of eDiscovery professionals is a complex and time-consuming process. 

Resources such as eDiscovery Assistant can help make this process more efficient and less time-consuming. eDiscovery Assistant includes a curated database of case law, rules, checklists, and forms, and a glossary of terms and was founded in 2016 by Kelly Twigger, the Principal at ESI Attorneys and a nationally known eDiscovery attorney, author, and speaker.

As a partner of eDiscovery Assistant, Onna's team of eDiscovery experts uses the platform to stay informed on developing case law, rules, and technology's impact on the evolving eDiscovery landscape. 

HID GLOBAL CORPORATION, v. VECTOR FLOW, INC.

A recent development in HID GLOBAL CORPORATION v. VECTOR FLOW, INC. stood out to our team because it centers around the format and security of ESI production.

In this case, HID alleges "trade secret misappropriation, breach of fiduciary duty, and breach of contract." HID requested a direct inspection of Vector Flow's "live Jira system" rather than reviewing exported Jira tickets in a spreadsheet to address allegations that Vector Flow was deleting and modifying information in its Jira database.  

Michelle Kovitch (@Michelle K), Strategic Solutions at Onna, who has 20 years of paralegal and litigation support management experience, stressed how this case points back to the ESI protocols that should be established early on in a matter and the importance of all parties understanding how data is stored and what they should expect for each cloud application.

Tim Thames (@Tim Thames), Senior Account Executive at Onna with 28 years of legal services and eDiscovery experience, agrees. "As Michelle Kovitch mentions, it's really becoming the standard to know your data as early as possible and to understand your data sources." He added, "This case highlights the ABA rules on competence in technology. Now it's either learn it or hire someone that does."

Pedro de Lencastre (@Pedro), Customer Success Director at Onna shared his key takeaways based upon his legal and eDiscovery experiences, “As recently discussed by our Alternative Data panel at Legal week, I expect to see more courts being asked to weigh in on the collection requirements related to new cloud-based applications. In Vector Flow, the court dealt with Jira and ordered the production of Jira tickets, including prefixes, change logs, comments, system audit logs, and custom fields. I advise customers to look for tools to prepare them for the future: what would you do if a court ordered you to produce Jira tickets with these requirements?”

Does your company use Jira? Does this development affect your organization’s data maps or workflows? Share your comments below.