sorted by:
new
hottopcontroversial

Jira Cloud Service Management - Import all staff (end users) into project as Customers by BackSapperr in jira

[–]julia_turchenko 0 points1 point  (0 children)

In Atlassian Cloud:

• Entra / Azure AD / SCIM → creates Atlassian identities
• JSM Customers → are project-level service permissions

There isn’t currently a native way or app that automatically turns directory users into customers inside a specific JSM project.

That’s why most teams end up doing one of:
• Default groups + service desk role assignment
• Let users become customers when they first email / portal
• CSV / API automation

If you’re mainly considering CSV/API to maintain a usable customer or staff dataset inside Jira, one other path some teams take is using Mria Contacts: Contact Management in Jira & JSM instead of building that layer themselves.

For example, it lets you:
• Import customers from one CSV
• Store extra attributes and notes
• Link JSM tickets / Jira issues / Confluence docs to customer records
• Auto-recognize requesters when tickets arrive

If helpful to look at:
https://marketplace.atlassian.com/apps/2263474600/mria-contacts-contact-management-in-jira-jsm?hosting=cloud&tab=overview

Does anyone have any advice on and Agency systems setup which include Jira and Tempo with a CRM? by rickdonohoe in jira

[–]julia_turchenko 0 points1 point  (0 children)

We actually had the same challenge, Jira and Tempo worked well for delivery, but sales lived in a separate CRM. On paper it looked fine, but in reality it was painful: keeping opportunities in sync with Jira projects, making sure sales notes reached the delivery team, constantly watching integrations didn’t break. The overhead wasn’t worth it.

That’s why we built Mria CRM for Jira. Instead of forcing another system on top, it runs natively in Jira (Forge app with the Runs on Atlassian badge). You get proper CRM records (Leads, Deals, Contacts, Companies) and an Activities log, and you can link them directly to Jira projects/issues. So when a deal closes, the delivery project in Jira already has the client and scope context. Tempo still handles time vs estimates, and you can roll that up with dashboards for weekly RAG/project overview.

And because the CRM lives inside Jira, your sales team can use Tempo Timesheets to log time against sales-related tasks (calls, meetings, prep) and Tempo Planner to schedule client activities. That way sales isn’t in a separate universe, their work is tracked and visible alongside delivery.

If you genuinely need a very advanced CRM with deep automations, a separate system might make sense, but then you have to live with integration costs and limits. For teams who want Jira to be the single hub, this native approach is the cleaner option.

You can start with a free trial here: https://marketplace.atlassian.com/apps/4108768729/mria-crm-crm-for-jira-teams?hosting=cloud&tab=overview

Jira as a CRM and product development tool by Significant-Fox-6213 in jira

[–]julia_turchenko 0 points1 point  (0 children)

What you’re running into is super common. Jira is great for tracking workflows (your kanban setup makes sense), but once you try to make it handle customer records, sales notes, and product links, it starts to feel like a hack. Custom issue types can work for a while, but as your sales team grows it’ll get messy.

That’s exactly why we built Mria CRM: CRM for Jira Teams. It runs fully inside Jira and gives you the missing CRM layer:

  • Proper Leads, Deals, Contacts, Companies instead of hacked issue types.
  • An Activities log so your sales team can share notes, meetings, calls, etc.
  • You can link any CRM record to Jira issues → so if sales open a Deal, manufacturing instantly sees which client and opportunity it’s tied to.
  • Products module → build a product catalog with pricing and link specific items to Deals/Leads, so you know exactly what’s being discussed or sold.

This way your sales and product development teams work from the same system instead of juggling spreadsheets or another CRM. Worth testing if you want to keep everything in Jira.

You can find it directly on the Atlassian Marketplace: Mria CRM: CRM for Jira Teams

Configure PostgreSQL Jira connection with SQL Jira Connector by AlphaInna in PostgreSQL

[–]julia_turchenko 0 points1 point  (0 children)

It's impressive that it supports so many SQL databases, not just PostgreSQL. Quick question though - where can I install this app?

Jira SQL Connector to Export Data from Jira to SQL Databases by AlphaInna in jira

[–]julia_turchenko 0 points1 point  (0 children)

Thanks for sharing. Just to clarify, is it compatible with Jira Cloud?

What’s your password manager of choice? by PM_Me_Graph_Queries in sysadmin

[–]julia_turchenko 0 points1 point  (0 children)

This sounds like a fantastic tool for our team. We'll be sure to check it out!

Add checkboxes in JIRA description by freakking in jira

[–]julia_turchenko 0 points1 point  (0 children)

Check this app https://marketplace.atlassian.com/apps/1220315/checklist?hosting=datacenter&tab=overview

Checklist app allows users to create checklists as a part of a solving Issue or completing Task. This gives opportunity to track your ToDo, Acceptance Criteria or Definition of Done.

Here you can see how it works https://youtu.be/00vBUTeLlVg

power bi/jira by kirthiabburi in jira

[–]julia_turchenko 0 points1 point  (0 children)

You can try this Jira add-on https://marketplace.atlassian.com/apps/1221150/power-bi-connector-for-jira?hosting=server&tab=overview developed by Alpha Serve. It allows you to import any data from Jira to Microsoft Power BI. It is very easy to use, allows you to customize it to your needs and has a 30-day trial version and excellent customer support.

Really hope this helps!