rss.livelink.threads-in-node

Access to my paid accound AND reset my password

Andrea O_Brien — Thu, 30 Jul 2026 14:55:22 GMT

Kimball International has a paid account thru Loom. I have been unable to access it since I got married and changed my last name as my account/login was tied to my former last name. I had our IT team add my old email address back and STILL NO LUCK getting the password reset link. Atlassian has a terrible business model with no customer service to speak of. I do NOT need a free trial account. I need access to my current and fully paid account. We are now unable to download any videos without upgrading but since I can't access my account, I'm unable to do anything. I do want all in this community to know how bad Atlassian is and the transition from Loom to Atlassian has been.

Need to get the information of a specific form field

C0666379 — Thu, 30 Jul 2026 14:22:34 GMT

I have a very long form in Jira, whose fields are used in a variety of automations or API calls. Because of this, I often need to get the id of a specific field in the forms, but, as far as I know, the only way to do this, is to call this specific API:

https://api.atlassian.com/jira/forms/cloud/{{CloudID}}/project/{{ProjectKey}}/form/{{FormID}}

Doing this and then logging {{webResponse.body.design.questions}} gets me the list of fields and their respective information, like this:

{381={choices=[], description=, label=New annual membership fee, questionKey=NewAnnualFee, type=tl, validation={rq=false}}

The number at the beginning, in this case, 381, is the one I need. The problem is, because the form is so long, the response doesn't fit in Jira's log response, so I often can't see the info of the exact field that I need.

I imagine there must be a way to log just the info for the field with a specific label or questionKey, but I'm having trouble making it happen.

I've tried doing

but that just returns the whole thing again

Possibilité de regrouper plusieurs cartes sous une carte commune

Maxime C2B Progrès — Thu, 30 Jul 2026 14:16:39 GMT

Bonjour,

Je ne pense pas que cette fonctionnalité existe, mais est-il possible de regrouper plusieurs cartes sous une carte commune (système mère / filles).

En cliquant sur la carte mère il serait possible d'afficher les cartes filles ou des les rétracter, et dans chaque cartes filles il serait indiquer le détail des items (check-list, pièces jointes...).

Exemple :

- Carte mère :

Développer le C.A. de mon entreprise

- Cartes filles :

Accentuer ma prospection

Participer à des salons

...

Merci d'avance de votre retour !

Maxime

SSO for Jira Sevice Managment

Luke Verheyden — Thu, 30 Jul 2026 14:08:32 GMT

My org now has guard. I have set up the SSO authentication policy in Atlassian user admin and added users into it.

Does mean that those users will now be able to use SSO to log into the help desk portal or is there another step.

I have set the portal to open under channel access and given test users service desk users permission in atlassian admin.

The reason I am asking is that I seem to get mixed results from users trying to log in.

[Feature Request] Expose AI Issue Summary as a persistent field / column in Issue Navigator and JSM

Alessandro Terribile — Thu, 30 Jul 2026 14:07:19 GMT

Hi Atlassian Community,

I'd like to suggest a feature improvement related to Atlassian Intelligence's AI-generated issue summary.

Current behavior:
The AI summary is generated on-the-fly when opening a single ticket and is displayed inside the issue detail view. However, it is not stored as a persistent field, which means it cannot be used as a column in the Issue Navigator, JSM queues, or any tabular/list view.

Requested behavior:
Allow the AI-generated summary to be persisted as a Jira field (either automatically or on demand), so that it can be:

Added as a column in the Issue Navigator
Added as a column in JSM queue views
Included in CSV/Excel exports
Used in dashboards and gadgets

Why this matters:
When managing a large number of tickets — especially in a support context — being able to scan AI summaries at a glance in a list view would dramatically improve triage speed and situational awareness. Right now, you have to open each ticket individually to read the AI summary, which defeats the purpose of having a queue or list view.

Suggested implementation:

Add a system field called something like AI Summary or Intelligence Summary
Populate it automatically when the AI generates the summary (or via a manual trigger / automation rule)
Make it available like any other field in column configuration

This would be a significant productivity boost for support and operations teams handling high ticket volumes.

Thanks for considering this!

Severe bug with Smart Links: All different URLs from the same domain are showing the exact same card

Paulo Eduardo Panazzo Azevedo — Thu, 30 Jul 2026 14:05:59 GMT

Hi everyone,

Around 10 days ago, Trello started forcing the exact same title/display text for all links belonging to a specific domain pasted into card descriptions.

Previously, each link showed its own individualized name or layout correctly. Now, even though the URLs are completely different and still redirect users to the correct, unique web pages when clicked, Trello forces the text/title of a completely unrelated past link onto all new ones.

I have already tried changing my Atlassian account settings under "Link Preferences" to "Display URL", but the system completely ignores this preference when saving the card description and still forces the incorrect title.

Manually clicking on every single link to change its display to "URL" is completely unfeasible for me, as we have hundreds of cards and thousands of affected links.

Is this a known issue with the recent Atlassian Smart Links global cache update? How can I completely disable this automated link fetching behavior across my boards to keep only the raw URL?

Thank you.

Login issues.

bon — Thu, 30 Jul 2026 14:01:39 GMT

Hi! I have this person, she’s a helper on a board I have. I added her to the board a month ago and made her a member but it said “Account not created yet” on there. I have her telling me now that trello is giving her issues. She sent a screenshot (the one I’ve attached) and said the “One last thing!” button does nothing when she clicks it. So she comes back a little after, saying she’s figured it out that she has an account but can’t log in, because the button on the screenshot she sent me does not work. I’m unsure of how else to help. I asked her if she checked her email and had anything she needed to verify but she didn’t respond to it. She just says the button does nothing. If anyone could help, I’d appreciate it very much.

Some assignees are missing in Jira Business Board Stand-up view

Megha Das — Thu, 30 Jul 2026 13:59:38 GMT

Hi everyone,

I'm using a Jira Business Board, and I've noticed that a few assignees don't appear in the Stand-up view, even though they have issues assigned to them. Other assignees show up as expected.

What could cause some assignees to be missing from the Stand-up view? Are there any board settings, filters, or permissions that affect which assignees are displayed?

Has anyone encountered this issue before? Any suggestions would be appreciated.

Thanks!

The Unwritten Layer

Dave Rosenlund _Trundl_ — Thu, 30 Jul 2026 14:32:13 GMT

Your systems don't run your operation. Your people do, along with everything they never wrote down.

The pattern I kept seeing

Over the past eight months, I've written about what prevents organizations from making AI work from several angles. A pattern emerged: AI often returns answers that are well written, confident, and wrong.

At first I blamed the usual suspects: messy, incomplete, or insufficient data and poorly crafted prompts.

If you follow this series, you've seen me circle and repeat this point.

Then I realized: that explanation isn't good enough.

We've only been looking at half of it

Say "AI is only as good as its data" and every practitioner in the room nods, because we've all lived it. Garbage in, garbage out. There's an entire industry pointed at that sentence.

But the conclusion is incomplete.

You can clean every record, reconcile every system, and pass every audit, and AI will still get things wrong.

Watch what your people do

Watch an experienced professional work and you can see the missing part, because they're the one supplying it.

They know which fields in the system are trustworthy and which are obsolete. And when the documented process and the actual one have drifted apart, they know who to ask.

None of this is anywhere you could look it up. It's judgment, built over years, applied so constantly that nobody notices it's there.

Here's what this looked like in practice

A colleague recently told me a story that captures this perfectly.

He'd worked with a change-management team in a larger enterprise. That team had twenty years of experience. And almost none of it written down.

They approved every change, insisting they had to, because they were the only ones who knew what would break. For years they were right. They'd seen the failures. They remembered the "routine change" that took the payment gateway down one Friday night, the one nobody had flagged as risky. They knew what depended on what.

And none of it was stored in a system.

Then Agile and DevOps arrived. The volume of change outran them, and the change-management team became a change-management queue.

People started routing decisions around them, because a process that can't keep up stops getting followed. The knowledge that made them valuable was the same thing that made them impossible to scale. It lived in their heads and nowhere else. If one of them left, twenty years of judgment left with them.

Here's the part worth remembering. Nobody entered bad data; there was barely any data to enter. The operation ran on people who knew things, and it ran fine, right up until it had to run faster than the people could.

I bet you know similar situations in your own organization.

The layer nobody documents

Recently, I started calling this the unwritten layer. The part of how an organization works that never made it into a system, because the people doing the work were the system.

It's the most valuable layer in the operation, and the only one that appears on no diagram, in no budget, in no governance model.

It isn't a problem to be solved. It's where expertise lives. The mistake is pretending it isn't there.

That layer doesn't hold itself together. It lives in a handful of people who cover the distance between what the record says and what's true. I've called that the human compensation layer, and it's the reason the gap has never really mattered.

AI can't see it

An AI agent has none of that. It can't read the room, ask the person who knows, or feel that a record is too stale. It only knows what's written, and it moves fast, before anyone can catch it.

Drop an agent where a person used to sit and the compensation just stops. Everything that used to get quietly corrected now gets executed.

So, when someone tells me a data-cleanup project is getting them ready for AI, I think they've done the part that's easy to see. But clean data doesn't create context. It just makes the absence of it easier to miss.

The work nobody wants to do

The same colleague eventually found a repeatable way through the company's change-management bottleneck, and it wasn't a cleanup project. He brought in a tool that scored change risk from history instead of memory and let the teams with a strong track record earn automatic approval on their low-risk changes, the way a bank approves a loan. The knowledge started moving out of a few heads and into something the whole organization could see. That was a few years ago.

Today, with GenAI on the table, he'd go further and sit the most experienced person down to build an agent that carries their judgment directly.

Call that what it is. It isn't documentation. It's capture, and it's the actual work most AI programs haven't started, because it's slower and less satisfying than buying another tool.

What AI is about to reveal

Here's where I've landed, after writing enough of these articles.

None of it was ever written down, because a person was always there to supply it. That held for exactly as long as the person stayed in the loop. And the loop is what we are automating.

The bigger thing is what that exposes. Today, most of us worry about whether our data is ready for AI. Now I think that was always only half the question.

The other half is whether we ever understood our own operations well enough to write them down, or whether we just had good people quietly making up the difference.

Most of us are about to find out. AI may not break your operation. But it will reveal it for what it is: one that relies on unwritten rules and knowledge.

📚 Further Reading

This article is part of an AI That Works article series, and it's the one I'll point back to when this idea comes up again, instead of retelling it each time.

In particular, check out what happens when AI reads a broken CMDB literally, and why the systems that look automatable often aren't for more context.

How to turn off notifications for maintenance items

Ben Cavallaro — Thu, 30 Jul 2026 13:43:31 GMT

I have a daily scheduled maintenance item that is long running that I dont want to receive notifications about. I unchecked the "Send Notifications" checkbox in the maintenance item itself, but as soon as I do that and hit Update, it reverts back to a checked state. Is this a bug, or is there some sub-component or other setting thats causing this value to revert back?

Can you manage alert layout in operations?

Natalie Waters — Thu, 30 Jul 2026 13:39:26 GMT

We've just migrated from OpsGenie and the loudest noise around the migration is around the layout.

Has anyone been able to change this or is there a feature ticket already open about this that we can follow?

We plan on implementing the workaround of using automations to update the description but would ideally like to just move the Extra Properties up where it's more visible

PRIORITY filed is not visible one editing the bug : Jira Cloud (Spaces experience)

Kamal — Thu, 30 Jul 2026 13:30:16 GMT

The Priority field is available while creating a Bug issue, but immediately after the issue is created, the Priority field disappears from the issue Details panel, making it impossible to edit the priority.

Formula Field Missing

Taylor Christensen — Thu, 30 Jul 2026 13:28:13 GMT

I was excited to find out that we can use a formula for our fields, but my admin is not finding the formula option in the "create new field." He will search for it, and nothing generates. We have the premium version of Jira. Is this option hidden or do we need to contact someone to access this field?

Rovo Agent: GitHub MCP Authentication Error in Slack

Vladyslav Berezhetskyi — Thu, 30 Jul 2026 13:21:33 GMT

Hello everyone,

I’ve created a Rovo Agent in Atlassian Studio and integrated it into our Slack channel. While the native Jira and Confluence skills are working perfectly, I’m having trouble with the GitHub MCP (Model Context Protocol) integration.

The Goal:
I want the Rovo Agent to be able to retrieve logs and status information from GitHub Actions pipeline links or specific repositories mentioned in Slack.

The Problem:
Even though I have enabled the GitHub MCP server and all its associated skills in the Agent configuration, every time I ask a question that requires GitHub access, Rovo responds with:

"This response was generated without using the following MCP server(s), because you're currently not authenticated. Your response quality may improve if you authenticate to these servers. Select the server(s) you'd like to authenticate to:"

What I’ve Tried:

Verified the GitHub MCP is enabled in the Agent's "Skills" section.
Ensured the Agent has the correct instructions to use GitHub tools.
Checked that my Atlassian account is linked, but the prompt for GitHub authentication keeps appearing.

Questions:

Is there a specific step to perform a "Service Principal" or "Admin-level" authentication for the GitHub MCP so the Agent doesn't require individual user auth every time?
Are there specific OAuth scopes or GitHub Organization settings (like third-party application restrictions) that might be blocking Rovo from maintaining a session?
How can I ensure the Agent uses the authenticated connection to parse pipeline links?

Any guidance on how to fix this authentication loop would be greatly appreciated!

Infosysta Apps is Now Part of Futurate 🎉

Elie Iskandar - Infosysta Apps — Thu, 30 Jul 2026 13:11:47 GMT

We're excited to share an important milestone in our journey: Infosysta Apps has officially become part of Futurate.

Same apps. Same team. Same commitment — now backed by a lot more firepower.

Here's the short version: nothing changes for you today, and what's coming next only makes things better. The tools you've relied on for your Atlassian ecosystem are now part of a broader, AI-powered platform built to help businesses work smarter, faster, and with greater confidence.

Why This Matters

Over the years, Infosysta Apps has been built on a simple principle: create reliable, high-quality solutions that solve real problems for real teams. That principle hasn't changed — what's changing is our capacity to deliver on it.

As Futurate, we're combining the product expertise you already trust with an expanded suite of AI-driven tools and intelligent automations, all under one unified company built for the future of work.

What Stays the Same

We know change can raise questions, so let's be direct about what this means for you:

Your apps, licenses, and subscriptions remain unchanged — nothing about your current setup requires action from you.
The same team, the same support — the people who've supported your account are still here, still committed to your success.
Continued updates and innovation — you'll keep receiving the product improvements and reliability you've come to expect, now backed by even greater resources.

What's New

Under Futurate, you'll have access to a wider range of AI-powered tools built for modern, fast-moving businesses. Whether you stick with your Atlassian tools today or grow into broader automation and AI capabilities tomorrow, Futurate is built to scale with you.

Learn More

We invite you to explore our new home and discover what's ahead: 🌐 futurate.ai

Thank You

This transition is only possible because of the trust our customers have placed in us over the years. We're grateful for that trust, and just as committed to earning it every day as Futurate.

Here's to the next chapter — thank you for being part of it.

— The Futurate Team (Formerly Infosysta Apps)

Have questions about this transition? Reach out to our team anytime — we're here to help.

📖 Originally published on the Futurate blog: Infosysta Apps Acquired by Futurate

i need access to

lrossi — Thu, 30 Jul 2026 13:00:45 GMT

please help me, I am not able to open the form

Conditional fields in Jira - without scripting

Maciej Dudziak _Forgappify_ — Thu, 30 Jul 2026 12:44:49 GMT

If you manage Jira, you have probably hit this wall: a field that should only appear for bugs shows up on every work type. "Steps to reproduce" clutters a change request. "Rejection reason" is optional when it should be required. You know the screen is messy, but fixing it feels like opening a can of worms.

Screens and field configurations get you part of the way. But conditional behaviour - show this field only when that option is selected, require this field only for bugs - is not something they can do. That either means a scripting plugin and a developer to maintain it - or accepting the limitation.

Field Rules - UI Modifications for Jira is built for that gap. You configure conditional logic on Jira screens yourself, in the admin page - no scripting, no developer, no workflow changes. When requirements shift, you make the update yourself, the same day.

What a rule looks like

A rule has two parts: a condition and an action.

The condition describes when the rule applies - based on the value of another field, the work type, the space, or who is viewing it: their role, group, or identity. The action describes what happens - show a field, hide it, make it required, lock it, pre-fill it, or filter its options.

You configure rules in the Field Rules admin page. The same rule works on Jira work item screens and the JSM customer portal alike.

What you can do with it

Show and hide fields based on what's selected

A field on a Jira screen is either always visible or always hidden - there is no in-between. A "Vendor contact" field clutters every work item regardless of whether a vendor is involved. You can remove the field from the screen, but then it disappears for everyone - not just the cases where it is irrelevant.

With Field Rules, a field can be hidden by default and revealed only when a specific condition is met.

Example: a team tracks work items linked to external vendor tools. The "Vendor Tool Link" field should only appear when the account source is set to a specific vendor. One rule: show "Vendor Tool Link" when "Account Source" equals "Apex Cloud". For everything else, the field stays hidden. The field appears only where it's actually needed, instead of the all-or-nothing choice you'd otherwise be stuck with.

Branch into different field sets

When different request types need different fields, the usual workaround is separate work types - one per path, each with its own screen. Three paths means three work types, three screens, and three places to update when something changes.

With Field Rules, a single select field acts as a router instead. Different options reveal different sets of fields, each made required for that path.

Example: an operations team receives several types of internal requests. Choosing "System Configuration" reveals a "System Details" field and makes it required. Choosing "Performance Metrics" reveals a different field. Choosing "General Inquiry" reveals a notes field. One work type handles all paths cleanly.

Filter options based on another field

When two fields are related - component and sub-module, category and sub-category - nothing in standard Jira prevents users from selecting a combination that does not make sense. A reporter picks "Axiom CRM" as the component, then selects a sub-module that belongs to a different product entirely. The bad data goes through.

With cascading options, the child field filters automatically based on what the parent field contains.

Example: a platform team uses a "Component" field and a "Sub-module" field. Selecting "Axiom CRM" narrows Sub-module to three relevant options. Selecting a different component shows a completely different set. Invalid combinations are never selectable. That keeps the data clean at the source - no bad combinations to catch later in a report or clean up in bulk.

Restrict field access by role or group

Jira Cloud has no field-level permissions. A field is either on the screen for everyone or off it for everyone. If you want triage fields that only QA Leads should fill in, you have no native way to enforce that - you can hide the fields from everyone, or show them to everyone.

Field Rules lets you show, hide, or lock fields based on the current user's role or group.

Example: a QA team tracks defect reports. Root Cause and Impact Score are visible to everyone - but locked for everyone except QA Leads. Four additional triage fields are only visible to QA Leads at all. Everyone else sees fewer fields. Sensitive or specialist fields stay in the hands of the people who should be filling them in, and you are not relying on people to just know not to touch a field.

One place, not three

Behind every pain point above sits the same limitation: Jira cannot make a field behave conditionally on its own. Without a way to fix that directly, admins reach for whatever comes closest - a second work type, a duplicate screen, a separate field context per space. Each one gets close, but none of them actually branches on a condition, so admins end up maintaining near-identical copies side by side: screens that are almost the same field by field, field contexts holding almost the same option lists, work types someone has to remember to pick correctly when creating a work item. When one of them gets updated and the others do not, the setup quietly drifts out of sync.

With Field Rules, that duplication is not needed. One rule holds the condition and the action together, scoped to the spaces and work types it applies to. There is nothing to keep in sync, because there is only one place the logic lives.

The result: cleaner screens, fewer invalid entries, and fields restricted to the right people.

Field Rules is free for teams of 10 users or less, with a 30-day trial for larger teams: Field Rules - UI Modifications for Jira

What is the best Enterprise Test Management Software for Jira users?

Vinayak Wagh — Thu, 30 Jul 2026 12:42:21 GMT

We've evaluated several enterprise test management tools over the past few months. Some of the popular options we looked at were Xray, Zephyr, and TestRail.

Xray is a strong choice if your team wants deep Jira integration and advanced traceability.
Zephyr is widely used by Jira teams and offers a familiar experience for test management.
TestRail is known for its mature test case management and reporting capabilities.

Our team chose Tuskr because it provided the features we required without making the interface overly complicated. It has strong test case management, test runs, reporting, and custom fields. all while being much easier for new team members to learn.

The best tool really depends on your team's workflow, budget, and how much complexity you're willing to manage.

What has your experience been with enterprise test management software? I'd love to hear which tool you're using and what you like (or dislike) about it.

How to create a Resource Utilization report in Jira Software Cloud?

Alexander — Thu, 30 Jul 2026 12:28:48 GMT

Can we create a Resource Utilization report in Jira Software Cloud?

Does anyone know if this is possible or can point me in the right direction?

How can I move a work item to backlog?

Faheem Maker — Thu, 30 Jul 2026 12:25:23 GMT

In Jira, we previously had an option to select the ellipses icon on a work icon, click move > Backlog

After the change, all tickets on my board are no longer showing this option

In other words, can someone please tell me how to move a work item back to backlog from an scrum board?