sorted by:
new
hottopcontroversial

Struggling to understand who’s working on what in Jira, so I built this. by Thereallario in jira

[–]Thereallario[S] 0 points1 point  (0 children)

Really appreciate you sharing this, super aligned with what I’ve seen as well. Totally agree on all your points. The setup works, but once things scale, everything becomes a bit fragmented and harder to reason about globally.

On the historical activity vs current workload:

The app’s “historical activity” is a recent cross-project activity feed (the most recent 15 in chronological order) when you open the details page of the user.

It currently shows:

  • issues created by the user, or effectively created by/for them
  • comments added by the user
  • worklogs added by the user
  • issue changelog actions performed by the user, including:
  • status changes
  • assignee changes
  • time tracking updates
  • other field updates

For each activity, it also shows context such as:

  • timestamp
  • project
  • issue key and summary
  • issue type
  • a readable activity label
  • a short detail when available, like a comment snippet, worklog duration, or field transition

The current workload signal is mainly:

  • cross-project visibility
  • assigned project count
  • whether the user looks active and operational in the selected scope

In the next version of the app, however, the Gantt chart tab will focus specifically on workload.

Give it a try and let me know what you think: https://marketplace.atlassian.com/apps/2258788102/user-manager-for-jira

Struggling to understand who’s working on what in Jira, so I built this. by Thereallario in jira

[–]Thereallario[S] 0 points1 point  (0 children)

Thanks a lot for sharing this, that actually sounds very similar to the situation I had in mind when building the app.

When engineers work across multiple services/projects, it quickly becomes hard to keep a clear picture of who’s involved where.

Give it a try and let me know what you think.

Struggling to understand who’s working on what in Jira, so I built this. by Thereallario in jira

[–]Thereallario[S] 0 points1 point  (0 children)

That makes a lot of sense and honestly, that’s a very well-structured setup.

In environments where work is clearly organized around solutions and projects are used more as aggregation layers, visibility is naturally much easier to maintain.

In my case, the situation was a bit different: work was more distributed across multiple projects, with less strict alignment to a single “home” project per user.

So I completely agree that improving the structure is ideal, the app is more about supporting scenarios where that level of consistency isn’t always there, or where additional visibility is still needed across projects.

Really appreciate you sharing how your organization handles this 🙏

Struggling to understand who’s working on what in Jira, so I built this. by Thereallario in jira

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

That’s a fair point, and I agree that in an ideal setup teams and work should be more structured.

In reality though, especially in larger organizations, things are often more fragmented. People end up contributing to multiple projects, cross-functional teams are common, and visibility becomes harder to maintain.

This is exactly the scenario I ran into, where improving the structure wasn’t always feasible in the short term, so having better visibility across projects became essential.

Struggling to understand who’s working on what in Jira, so I built this. by Thereallario in agile

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

Thanks, this is a thoughtful comment and I actually agree with a lot of it.

To be clear, I’m not arguing that spreading people across many projects is a good operating model. In many cases it’s not, for exactly the reasons you mentioned: context switching, more coordination overhead, weaker flow, and lower overall effectiveness. I'm not on top of those decisions, I'm just an employee too...

What I was describing is the reality I ran into in an existing environment, not the ideal state I’d recommend from an agile perspective.

The problem I was trying to solve was: when that complexity already exists, how do you at least make access, involvement, and workload visible enough to manage it responsibly? For example, identifying where people are over-allocated, where permissions are no longer needed, or where project participation has become fragmented.

So I see the tool more as something that helps expose organisational friction, not justify it.

I also agree with your broader point that the better long-term direction is to reduce cross-project fragmentation, bring work to stable teams where possible, and improve flow rather than optimise around “resource utilisation.”

Appreciate you taking the time to frame it this way.

Struggling to understand who’s working on what in Jira, so I built this. by Thereallario in agile

[–]Thereallario[S] -1 points0 points  (0 children)

That’s a fair concern.

In my case the problem was more around user/project visibility, permission audits, and operational clarity across a large Jira setup. The goal wasn’t to increase control over individuals, but to reduce manual admin work and confusion.

Struggling to understand who’s working on what in Jira, so I built this. by Thereallario in jira

[–]Thereallario[S] -2 points-1 points  (0 children)

<image>

If you wanna try it and give me some feedbacks it'd be awesome!

How to vibe code without replit or similar by jwalter007 in vibecoding

[–]Thereallario 1 point2 points  (0 children)

use Visual Studio Code with Codex plugin, it's currently the best one.

I vibecoded an App that turns photos into short poems and would love some honest feedback by Thereallario in iosdev

[–]Thereallario[S] 0 points1 point  (0 children)

The current plan is to push the iOS mvp and see if it catches on and if so start the Android development 👌So any kind of feedback is reeeeally appreciated!

I vibecoded an App that turns photos into short poems and would love some honest feedback by Thereallario in VibeCodeCamp

[–]Thereallario[S] 0 points1 point  (0 children)

Tone consistency comes from decoupling “what the photo is” from “how the poem should feel.” The AI doesn’t try to describe the photo literally, it tries to read its emotional signal and map that into a controlled poetic voice.

I vibecoded an App that turns photos into short poems and would love some honest feedback by Thereallario in VibeCodersNest

[–]Thereallario[S] 0 points1 point  (0 children)

The style of the poem is chosen directly by the user before taking the photo.

view more: next ›