Book a demo

Cut patent&paper research from weeks to hours with PatSnap Eureka AI!

Try now
TG-2006 Holdings v. Atlassian: US8583514B2 Patent Dismissed | PatSnap
Explore in Eureka
Case ID2:25-cv-00249
FiledMar 2025
ClosedMar 2025
Patent Litigation

TG-2006 Holdings v. Atlassian: Infringement Suit Dismissed With Prejudice in 23 Days

TG-2006 Holdings, LLC filed a patent infringement action against Atlassian Corporation in the Eastern District of Texas, asserting US8583514B2 covering a system and method for tracking information in a business environment. The case closed just 23 days after filing via joint stipulation, with each party bearing its own costs and fees.

Resolution time
23days
23 days — well below the multi-year median for E.D. Texas patent cases, suggesting early resolution
Patents asserted
1
US8583514B2 — system and method for tracking information in a business environment
Outcome
Dismissed with Prejudice
Joint stipulation under Rule 41(a)(1)(A)(ii); plaintiff cannot refile the same claims
Cost ruling
Each Party Bears Own Costs
No fee-shifting ordered; court directed each party to bear its own costs and fees
Published by PatSnap Insights Team · Verified by PatSnap Eureka Data
Case overview

A 23-Day Patent Suit Against Atlassian That Ended Before It Began

On March 2, 2025, TG-2006 Holdings, LLC filed a patent infringement action against Atlassian Corporation in the United States District Court for the Eastern District of Texas (Case No. 2:25-cv-00249), before Judge Rodney Gilstrap. The asserted patent, US8583514B2, covers a system and method for tracking information in a business environment — technology broadly relevant to enterprise workflow and project management platforms of the kind Atlassian commercialises.

The case resolved on March 25, 2025 — just 23 days after filing — via a Joint Stipulation of Dismissal With Prejudice submitted by both parties under Federal Rule of Civil Procedure 41(a)(1)(A)(ii). Judge Gilstrap accepted and acknowledged the stipulation, dismissing all of plaintiff’s claims against Atlassian with prejudice and ordering each party to bear its own costs and fees. All pending relief requests were denied as moot.

The 23-day resolution is notably swift even by the standards of patent cases that settle early, and is consistent with a pre-litigation licensing negotiation that concluded either in a private settlement or a mutual decision to abandon the action. The public record is silent on whether any financial terms were agreed; the ‘each party bears own costs’ language only confirms the court imposed no fee award, not that no commercial arrangement exists between the parties.

Case at a glance
Case no.2:25-cv-00249
CourtTexas Eastern
JudgeRodney Gilstrap
FiledMarch 2, 2025
ClosedMarch 25, 2025
Duration23 days
OutcomeDismissed with Prejudice
Verdict causeInfringement Action
BasisDismissed with Prejudice
Prior Art Intelligence
See what prior art exists on this patent.
Eureka scans millions of patents and papers to surface prior art that may have invalidated these claims before costly litigation begins.
Check Prior Art
Case data sourced from PACER / Texas Eastern District Court via PatSnap Eureka Litigation Intelligence Explore similar cases ↗
Case timeline

Filing to Dismissed with Prejudice in 23 days

23 days — well below the multi-year median for E.D. Texas patent cases, suggesting early resolution

Case timeline: Complaint filed MAR 2 2025, MAR–APR — 23 days total Horizontal timeline showing the three key events in TG–2006 Holdings, LLC v Atlassian Corporation from filing to resolution. Source: PACER, Texas Eastern District Court. MAR 2 2025 Complaint filed Pre-trial proceedings MAR 25 2025 Dismissed with Prejudice 23 DAYS TOTAL
Dismissal terms

Dismissed with prejudice: what the joint stipulation means for both parties

Legal mechanism

Rule 41(a)(1)(A)(ii) dismissal with prejudice: the action is permanently closed

A stipulated dismissal with prejudice under Rule 41(a)(1)(A)(ii) requires both parties to sign the stipulation — meaning Atlassian consented. Critically, ‘with prejudice’ operates as an adjudication on the merits: TG-2006 Holdings cannot refile the same claims based on US8583514B2 against Atlassian. The res judicata bar is permanent for this plaintiff-defendant pair on these specific claims.

Permanent bar on re-filing
Plaintiff outcome

TG-2006 Holdings surrenders the right to pursue Atlassian again on this patent

By agreeing to dismiss with prejudice, TG-2006 Holdings permanently forecloses further litigation against Atlassian on US8583514B2. Whether this reflects a licensing resolution, a weakness in the infringement case, or a strategic withdrawal is not disclosed in the public record. The ‘each party bears own costs’ term suggests no court-ordered compensation, though a private commercial arrangement cannot be ruled out.

Claims barred — no public terms
Defendant outcome

Atlassian secures permanent dismissal — and consented to the terms

Atlassian’s agreement to a mutual stipulation rather than pursuing a fee motion under 35 U.S.C. § 285 suggests the parties reached a clean resolution. The with-prejudice bar protects Atlassian from any subsequent action by TG-2006 Holdings on the same patent. Atlassian absorbs its own legal costs but avoids protracted E.D. Texas discovery and trial risk on enterprise workflow IP.

Protected from re-litigation
Commercial implications

Swift closure limits precedent risk for Atlassian’s broader product portfolio

US8583514B2 covers business information tracking methods potentially applicable across Atlassian’s Jira, Confluence, and Trello product lines. A 23-day resolution — before any substantive briefing — means no claim construction, no validity ruling, and no infringement finding enters the public record. This limits the precedential exposure but leaves the patent’s enforceability against other enterprise software defendants unresolved.

No claim construction on record
Legal analysis based on PACER docket records for case 2:25-cv-00249 and PatSnap Eureka litigation intelligence Search PatSnap Eureka ↗
Parties and representation

Full party and counsel information

RoleNameTypeDetail
PlaintiffTG–2006 Holdings, LLCCompanyPatent assertion entity — holder of US8583514B2 (business information tracking systems)Search in Eureka ↗
DefendantAtlassian CorporationCompanyAtlassian Corporation — enterprise software company, maker of Jira, Confluence, and TrelloSearch in Eureka ↗
Plaintiff counselIsaac Phillip RabicoffAttorneyCounsel for TG–2006 Holdings, LLCSearch in Eureka ↗
Plaintiff law firmRabicoff Law LLCLaw FirmRepresenting TG–2006 Holdings, LLCSearch in Eureka ↗
Presiding judgeJudge Rodney GilstrapJudgeTexas Eastern District CourtSearch in Eureka ↗
Official verdict

Official order — verbatim text

“Before the Court is the Joint Stipulation of Dismissal With Prejudice (the “Stipulation”) filed by Plaintiff TG–2006 Holdings, LLC (“Plaintiff”) and Defendant Atlassian Corporation (“Defendant”) (collectively, the “Parties”). (Dkt. No. 6.) In the Stipulation, the Parties “stipulate to dismiss this action with prejudice,” pursuant to Rule 41(a)(1)(A)(ii) of the Federal Rules of Civil Procedure. (Id. at 1.) Having considered the Stipulation, the Court ACCEPTS AND ACKNOWLEDGES that Plaintiff’s claims against Defendant in the above-captioned case are DISMISSED WITH PREJUDICE. Each party shall bear its own costs and fees. All pending requests for relief in the above-captioned case between Plaintiff and Defendant not explicitly granted herein are DENIED AS MOOT. The Clerk of Court is directed to CLOSE the above-captioned case as no parties or claims remain. . ____________________________________ RODNEY GILSTRAP UNITED STATES DISTRICT JUDGE So ORDERED and SIGNED this 25th day of March, 2025”
Source: PACER Docket, Case 2:25-cv-00249, Texas Eastern District Court

The Court’s order accepts the parties’ joint stipulation verbatim, confirming dismissal with prejudice under Rule 41(a)(1)(A)(ii). The ‘with prejudice’ designation is legally significant: it functions as a final adjudication on the merits, permanently barring TG-2006 Holdings from reasserting the same claims against Atlassian. The absence of any fee award under 35 U.S.C. § 285 and the mutual cost-bearing instruction indicate neither party sought to characterise the case as exceptional — consistent with a negotiated exit rather than a contested outcome.

PACER case 2:25-cv-00249 · Public docket record Explore in Eureka ↗
Patent at issue

US8583514B2 — System and method for tracking information in a business environment

Publication No.US8583514B2
Application No.US10/918037
Patent details
ProductSystem and method for tracking information in a business environment
Cited in actionMarch 2, 2025

US8583514B2 (application number US10/918037) claims a system and method for tracking information in a business environment — a technology domain that intersects with enterprise project management, task tracking, and workflow automation software. The patent’s application number format suggests a filing predating modern agile software tooling, meaning the claimed methods may read broadly on contemporary implementations in platforms such as Jira, Confluence, and comparable enterprise collaboration tools.

From a competitive intelligence standpoint, US8583514B2 sits in a technology space where multiple large enterprise software vendors — including Atlassian, Microsoft, Monday.com, and Asana — deploy products that could plausibly overlap with broad business information tracking claims. The absence of any IPR or PGR challenge on the public record means the patent’s validity has not been tested at the PTAB level, leaving it as a live enforcement asset for TG-2006 Holdings against other defendants in this sector.

Patent data sourced from USPTO via PatSnap Eureka patent database Search patent records in Eureka ↗
Freedom to operate

Should you run an FTO analysis against US8583514B2?

Any enterprise software company offering project management, task tracking, workflow automation, or business information management features should treat US8583514B2 as a potential FTO concern. The patent’s broad subject matter — a system and method for tracking information in a business environment — combined with its untested validity and an active PAE holder willing to litigate in E.D. Texas, makes it a credible risk vector for product teams shipping or updating workflow software.

PatSnap Eureka’s FTO Search Agent can map the claim scope of US8583514B2 against your product architecture, identify prior art that could support an invalidity position, and surface any continuation or family patents that may extend the enforcement footprint. Running this analysis before a litigation demand arrives is substantially more cost-effective than responding to a complaint filed in Judge Gilstrap’s court.

PatSnap Eureka FTO Search

Run a freedom-to-operate analysis on US8583514B2 to assess your product’s exposure

Run FTO in Eureka →
Related litigation

Similar patent infringement cases: business-method software in E.D. Texas

Explore related patent infringement cases involving business information tracking and enterprise workflow software patents litigated in the Eastern District of Texas.

🔍
Access 40+ similar cases in PatSnap Eureka
TG–2006 Holdings, LLC patent enforcement history, Texas Eastern case history, TG–2006 Holdings, LLC’s full IP portfolio, and comparable case analysis
PAE vs. enterprise SaaSE.D. Texas software patentsAtlassian IP litigation historyBusiness-method patent cases
Unlock similar cases in Eureka →
Strategic implications

What this case signals for the enterprise software IP landscape

A 23-day lifecycle in E.D. Texas is a leading indicator of pre-litigation leverage — not courtroom resolution.

E.D. Texas remains the venue of choice for business-method patent assertions

Despite post-TC Heartland venue reforms, TG-2006 Holdings filed in the Eastern District of Texas. Judge Gilstrap’s docket continues to attract patent assertion entities targeting enterprise software companies. Teams monitoring competitors’ litigation exposure should track E.D. Texas filings on business-process patents as an early-warning signal.

A with-prejudice stipulation in 23 days strongly suggests off-record settlement

The combination of mutual consent, extreme speed, and ‘each party bears own costs’ language is consistent with a confidential licensing resolution concluded before substantive litigation commenced. Enterprise software IP teams should model pre-litigation licensing outreach as a cost-effective response to early-stage PAE assertions on business-method patents.

🔒
Full strategic analysis in PatSnap Eureka
Unlock gated insights on PAE assertion strategy and enterprise software patent risk in the E.D. Texas District Court.
Continuation patent riskPAE portfolio mappingFTO for workflow software
Unlock full analysis →
Analysis powered by PatSnap Eureka Litigation Intelligence Explore in Eureka ↗
Frequently asked questions

TG–2006 v Atlassian — key questions answered

Still have questions? PatSnap Eureka can answer them instantly from patent and litigation data. Ask Eureka ↗
PatSnap Eureka

Don’t wait for a complaint — run your FTO on US8583514B2 now

TG-2006 Holdings retains full enforcement rights and no validity ruling is on record. PatSnap Eureka can map claim exposure across your product portfolio and monitor PAE activity in the enterprise software space before litigation lands.

Ask anything about this case.
PatSnap Eureka searches patents and litigation data to answer instantly.
Powered by PatSnap Eureka
Link copied to clipboard

Related Litigation Cases

Help us improve this page

Found incorrect or outdated information? Let us know and we'll get it fixed.