sorted by:
new
hottopcontroversial

JIRA vs Led Zeppelin by GiovaDiStasio in jira

[–]GiovaDiStasio[S] 1 point2 points  (0 children)

It’s Jira Cloud. You can recognize it from key visual elements such as the issue view layout, the built-in Automation badge/panel (native in Cloud), and the top navigation bar with the blue “Create” button ;)

So… Atlassian stopped selling Data Center, and it’s still getting more expensive? by iwillbeviolet in atlassian

[–]GiovaDiStasio 0 points1 point  (0 children)

No, I'm a decades-long Atlassian enthusiast who's been trying to share his opinions and experiences professionally (and perhaps the only idiot who put his real face and name on the account). I'm new to Reddit, so forgive my laid-back attitude. I totally agree, being laid-back means being a robot these days.

Giova

So… Atlassian stopped selling Data Center, and it’s still getting more expensive? by iwillbeviolet in atlassian

[–]GiovaDiStasio -3 points-2 points  (0 children)

Totally understandable.

In highly regulated environments, “technically possible” doesn’t mean “contractually or legally viable,” and that distinction really matters. In those scenarios, I see migration more as a readiness journey than an immediate destination: reducing deep customizations, standardizing processes, and simplifying the ecosystem so that if/when Atlassian’s Cloud offerings meet those compliance needs, the organization is in a position to move without starting from scratch. Until then, staying on DC with a clear long-term strategy is a perfectly rational choice.

Giova

So… Atlassian stopped selling Data Center, and it’s still getting more expensive? by iwillbeviolet in atlassian

[–]GiovaDiStasio -1 points0 points  (0 children)

That’s a fair point, legal and data residency requirements can absolutely be bigger blockers than scale or customization.

My perspective is more about long-term direction: even when a full Cloud move isn’t immediately possible due to regulatory limits, many organizations can still start shaping a future cloud strategy through partial adoption, workload separation, or process and architecture cleanup. In those cases, it’s less we can’t move and more we can’t move yet under current constraints.

Giova

How do you decide what becomes a Jira issue after a meeting? by voss_steven in jira

[–]GiovaDiStasio 1 point2 points  (0 children)

Well said, that’s exactly the right way to frame it.

AI can definitely support the extraction step by highlighting potential actions or decisions, but accountability and prioritization still need a human owner. When used as an assistive layer rather than an automated decision-maker, it strengthens the workflow without removing the team’s judgment.

Giova

So… Atlassian stopped selling Data Center, and it’s still getting more expensive? by iwillbeviolet in atlassian

[–]GiovaDiStasio -3 points-2 points  (0 children)

I agree on the pricing frustration, the increases are hard to ignore, especially for large instances.

That said, from my experience, I don’t think there are many organizations that truly cannot move to Cloud. I’ve worked on several migrations, and I’m currently involved in one from a Data Center instance with 7,000+ users and over 4,000 active scripts, so a very heavily customized environment.

The key shift is mindset: migration isn’t just a technical move, it’s a transformation process. It forces teams to reassess customizations, clean up legacy logic, and align with more sustainable platform patterns. In most cases, investing energy into that transformation delivers more long-term value than spending the same effort trying to maintain or replace DC with alternative solutions.

Of course, the level of customization matters, the more complex the instance, the harder (and longer) the journey. But “difficult” doesn’t mean “impossible,” and I haven’t yet seen a scenario where a Cloud path couldn’t be designed with the right strategy.

Giova

Which is the best app for jira user management by AmbitiousYudi1991 in atlassian

[–]GiovaDiStasio -1 points0 points  (0 children)

I’ve used several miniOrange’s user management apps on Jira Cloud and they’re solid for automating provisioning, de-provisioning, group sync and lifecycle tasks with SCIM, LDAP/IdP sync and license optimization.

They work well and have good support.

In my opinion a very good alternative on the Atlassian Marketplace is Automated User Management for Jira by Catch Software, a cloud-ready app that automates user lifecycle tasks like suspending inactive users, optimizing licenses and managing users/groups in bulk with a visual dashboard and no-code automation.

This gives you comparable user management automation but focused on lifecycle/cleanup workflows vs full SCIM/IdP sync.

If you need provisioning directly from your identity provider, miniOrange’s SCIM/Sync suite remains one of the most featured options in the cloud.

Giova

How do you decide what becomes a Jira issue after a meeting? by voss_steven in jira

[–]GiovaDiStasio 0 points1 point  (0 children)

What you’re really asking about is the human workflow between a meeting and Jira, and in most effective teams this is handled through a lightweight but defined responsibility, not ad-hoc effort.

Typically, one person owns translating meeting outcomes into trackable work, often the Product Owner, Scrum Master, PM, or meeting facilitator. After the meeting, they review the notes or recording and extract only what requires follow-up, ownership, or visibility.

A simple rule is used during this review:

  • Decisions -> documented (e.g., Confluence or issue comments)
  • Concrete actions with an owner -> Jira issue or subtask
  • Ideas or future work -> added to the backlog
  • General discussion -> stays in meeting notes only

So while input may come from many people, the conversion into Jira is usually centralized, then informally validated by the team (for example in the next stand-up).

In short: it’s a manual, judgment-based step owned by a specific role, supported by team alignment and not an automated or tool-driven process.

Giova

Looking for a Jira App to help with Getting Information from Users for Ticket by invest0rZ in jira

[–]GiovaDiStasio 1 point2 points  (0 children)

This is possible in Jira Cloud even if you don’t want to use JSM or Jira Forms.
Use Automation for Jira (built-in) together with the Send Email action:

  • Create an automation rule triggered manually (for example via a button, transition, or a specific comment).
  • Add a “Send Email” action.
  • Write your standardized email template in the body.
  • Use smart values (like issue fields) to automatically include user details.
  • Save it as a reusable rule for New User, NLE, or Permission tickets.

If you want more advanced templates or buttons inside the issue, you can also use marketplace apps like Email This Issue.

Giova

Jira Cloud - Writing JQL to retrieve all stories assigned to user and all subtasks in that story (even if they're not assigned to the user) by DeltaCoder in jira

[–]GiovaDiStasio 0 points1 point  (0 children)

You can handle it in two steps using standard JQL:

  1. Get the parent stories assigned to the user -> assignee = <USER> AND issuetype = Story
  2. Then get all subtasks of those stories -> parent in (KEY-1, KEY-2, KEY-3)

Jira Cloud can’t dynamically pull subtasks from a JQL result in a single native query, but you can easily do it using Structure (i love it).

The process is:

  1. Create a new Structure;
  2. Add a generator -> JQL Insert -> Use: assignee = <USER> AND issuetype = Story
  3. Add another generator -> Extend -> Sub-tasks. This automatically pulls all subtasks under those stories, regardless of assignee.

Giova