← Dealkeep
DocumentationPrivacyEULASupport

Dealkeep documentation (public knowledge base)

Getting started

  1. Install Dealkeep from the Atlassian Marketplace. A Jira admin opens Jira settings > Apps > Dealkeep to choose who can see and edit records (default: everyone), the default currency, and the stages of the Sales pipeline.
  2. Open Apps > Dealkeep CRM. On a new site it opens on Import and export: import your companies first, then contacts, then deals (see Importing). Or add records by hand with New company, New contact and New deal.
  3. On any Jira issue, open the Customer panel to link it to a company, deal or contact.

Companies, contacts and deals

  • Companies have a name, web domain, website, industry, phone, address, owner, tags and notes. The domain matters: contacts with an email at that domain join the company automatically, and the Customer panel suggests the company when an issue's reporter has an email at that domain. Webmail domains (gmail.com, outlook.com and others) are never used; admins can add more, such as partner domains.
  • Contacts have a name, email, phone, job title, company, owner, tags and notes.
  • Deals have a name, value and currency, pipeline and stage, expected close date, company, contact, owner and notes. Moving a deal to the Won or Lost stage closes it; moving it back reopens it. Lost deals ask for a reason.
  • Every record has an Activity timeline: add notes, calls, meetings, emails and tasks. Stage changes, merges and issue links are recorded as history (tick Show history to hide them). A company's timeline includes its contacts' and deals' activity.

Pipeline and forecast

  • The Pipeline tab shows one pipeline as a board. Drag a card to another stage, or use the stage list on the card. Won and Lost columns show deals closed in the last 30 days.
  • Each open stage has a probability. Weighted value = deal value x probability. The board shows open and weighted totals, deals won this month, the 90-day win rate and deals past their close date. Below the board, the forecast by expected close month.
  • A stage's Flag after days marks deals that sit there longer as stuck (yellow edge).
  • Admins can add pipelines (for example Renewals) and change stages in settings. Removing a stage that still has deals asks where those deals go.

Dashboard widget

Add Deal pipeline (Dealkeep) to a dashboard. Pick a pipeline, everyone's deals or the viewer's own, and an optional title. It shows open and weighted value by stage, the weighted forecast by close month and stuck deals. On the new Jira dashboards, changes apply when you save the dashboard.

Classic Jira dashboards and their gadgets stop working on 17 May 2027, when Atlassian retires them. Before then, add the widget to a new Jira dashboard and pick the same settings.

Linking Jira work

  • Customer panel (right side of every issue, any project): link a company, deal or contact by searching, or click a suggestion. Linking a deal also records its company.
  • Link issues by JQL on a company or deal: enter a query such as project = HELP AND reporter in (...) or labels = acme, click Check to see how many match (up to 200 per run), then Link. Jira checks the query first and shows its own error if a field or value does not exist.
  • Linked Jira work on each record lists the linked issues you can browse. Filter it with JQL, for example statusCategory != Done. Issues in projects you cannot browse are counted, not shown.
  • JQL fields for linked issues: dealkeepCompany, dealkeepDeal, dealkeepStage, dealkeepContact (email) and dealkeepValue (total value of linked open deals). Examples: dealkeepCompany = "Kestrel Robotics" AND statusCategory != Done, dealkeepStage = Negotiation, dealkeepValue > 50000 ORDER BY priority. They appear a few minutes after install. Renaming a company, moving a deal or merging records updates linked issues (up to 100 at once; larger sets update the next time each issue is linked or unlinked).

Duplicates and merging

  • When you save a new company or contact that matches an existing one (same domain or email, or the same name once Inc, LLC, GmbH, punctuation and "The" are ignored), Dealkeep shows the match and asks before saving a second record.
  • The Duplicates tab lists likely pairs: same domain, email or name (Duplicate), similar names or same phone (Possible).
  • Merge (Keep A or Keep B) keeps one record, fills its empty fields from the other, combines tags and notes, and moves contacts, deals, activity and linked issues onto it. The other record is deleted and the merge is recorded in the timeline.

Importing

  • Import and export > Import from CSV. Pick what the file contains, choose the file (up to 5,000 rows), and click Preview. Exports from HubSpot, Pipedrive and Salesforce work as they are; common column names are recognised (Company name, Company Domain Name, Organization - Name, Email, Person - Email, Deal Name, Deal - Value, Amount, Deal Stage, Close Date, Associated Company, owner columns by email or name, and more). Download a template from the Import tab to see the expected columns.
  • When a row matches an existing record you choose: fill in its empty fields (default; an import never moves a deal's stage or overwrites its value), leave it, or create a second record. Rows that match an earlier row in the same file count as matches too.
  • Contacts and deals name their company; turn on Create companies named in the file to add missing ones (their domain comes from the contact email when there is one). A deal row with a contact email creates the contact if needed.
  • HubSpot's default stage ids (appointmentscheduled, closedwon and so on) map to the stage with the nearest probability; other unknown stages go to the first stage, with a note.
  • The preview lists each row with what will happen and why. Large files import in batches; if an import stops, run it again with the same file: rows already imported are matched, not created twice.

Exporting

Import and export > Export downloads companies, contacts, deals, or all activity and tasks as CSV, in the same columns the importer reads.

Access and licensing

  • Admins choose who can see records and who can add and edit records by Jira group. Empty means everyone with access to the app. Jira admins always have full access.
  • If the subscription lapses, everything stays readable and exportable; adding and editing return when it is renewed.

Privacy

Dealkeep runs on Atlassian Forge. Records live in your site's Forge SQL database and never leave Atlassian. See the privacy policy for details, including how to answer a contact's deletion request.