C.Faysal {CFcon} Community Champion

@umashri Thanks, and yes, that would be a very useful direction. The current scope is primarily app footprint and dependency analysis. It tries to answer questions such as: Which apps are actually being consumed, where are they referenced, and what evidence do we have before making a migration decision? It does not…

Thanks @Jaume Guasch Gutsens you’re so welcome

Hey @Marcelo Montaño Sánchez Thanks, and yes, that’s a very relevant distinction. ScriptRunner is actually one of the reasons why we deliberately treat the output as evidence rather than as an automatic migration decision. The current footprint analysis can collect the relevant ScriptRunner artefacts, but it does not yet…

hey may be worth taking a look at Release Tracks in some scenarios best regards

Hi @Satyanarayana, I went digging on the jira-cost-based string, and there's an Atlassian ticket that clears up most of this: JRACLOUD-69262. It quotes the rate-limiting doc and lists the reason directly, so the value is real, not something your tenant invented: - jira-cost-based, which refers to counter and cost based…

Hi @Satyanarayana, Good follow-up, and thanks for sharing the actual numbers. The 400 to 800 jump is worth digging into, but I want to separate what the docs actually say from what the before/after sample can tell us, because they point in different directions here. Let me take your questions in an order that builds on…

Hi @James George Lance_ Jr can you please confirm this rule has both Spaces scoped correctly? afterwards we can continue the analysis thank you regards

Hi @Satyanarayana Worth separating two things up front, because provisioning user accounts and creating issues are different APIs with different limits. A few details in the report don't line up with Atlassian's documented model, so I'd start there: * Ratelimit-Reason: jira-cost-based isn't a documented value. The…

You’re welcome

Hi @Steven Mcgrew , Good question, and the error wording here is misleading. This isn't a move-permission problem, and it's not about being admin of your own page. The message is telling you the real reason: the page is restricted, and you don't have rights to create restricted content in the team space. A couple of things…

Hey @Ivan Andrieiev To be totally honest i didn't ran lots of cloud-to-cloud data transfers but let me summarize some findings from the official docs here for you. From what i've seen so far the "error with no explanation" almost always means the importer rejected rows but you're only seeing the summary screen. Two things…

From what i understand from your screenshot and the expected result it looks like you don't need a branch at all @Sara try this instead: here is the conditional part: One note on the 7-day check: NOT status CHANGED AFTER -7d catches any status transition. Your original statuscategorychangeddate only updates when a work…

Hi @Sara The cause is the branch. Everything, including the Transition action, is sitting inside the "For: Linked work items / is blocked by" branch. Inside a branch, {{issue}} no longer refers to the work item that triggered the rule, it refers to the branched (linked) item. Straight from Atlassian's docs: "All actions…

hey everybody https://www.linkedin.com/in/cfaysal/ happy to connect and exchange on forge development, AI engineering etc.... regards

Update. this seems to be fixed (finally)

Fair point on scaling, you're right. Throughput wasn't the blocker, "at scale" was sloppy framing on my part. The actual reason redirect wasn't an option: the source DC Confluence host had been decommissioned by the time we got involved. No DNS, no Apache, no server. The links in the Jira issues had become pure dead URLs.…

Great write-up, and a use case I ran into myself recently. We had a similar but slightly different scenario: Confluence had been migrated to Cloud, but Jira was still sitting on Data Center, holding 300k+ issue links pointing at the old Confluence DC URLs. No redirection layer was going to fix that at scale. I ended up…

thank you @Trudy P Claspill

Just a little heads-up @Snehal Singh . I fed your exact requirement into our Alchemist agent: "Add 3 issues in an epic with summary <abc>, <pqr> and <lmn>. Scheduled event with JQL. Make sure not adding it multiple times. If issue with summary abc is already present then same should not get added again." The core problem:…

Hi @Bill Sheboy, Thank you for pointing this out. You are right and I apologize - I used an AI tool to help draft the response and should have disclosed that clearly from the start. Best, cF

If anyone else besides @Julien Béchade is seriously interested in this, feel free to reach out. Once we have a clear picture of what the final state should look like, we'll wrap it up and submit it to the Marketplace - so everybody can use it for free. Drop a comment or connect with me directly. regards cF

Hi @Snehal Singh if i understood your desired goal correctly: The root cause of your issue Your single Lookup + Advanced Compare approach works on the first run because there are 0 child issues yet. On the second run, the lookup returns existing issues, and the Advanced Compare fails to evaluate correctly because it…

Would you like to see this live in a demo session @Julien Béchade ? maybe you have some additional feature requests to be added. let me know if you would need this solution. Happy to share it with anyone who does regards

Oh wait, I misunderstood your question @Julien Béchade By forms you mean ProForma in JSM? If so, the answer is unfortunately no since there is no direct implementation. You could map the custom field to a form, but Jira Forms doesn't recognize the custom rendering - it falls back to a plain text input instead of the…

@Julien Béchade if you want :)

Hi @Leticia Ovans You're right, Jira's native behavior is inconsistent here. System fields like Assignee show "(Deactivated)" clearly, but custom User Picker fields silently keep the old name. After a reorg or offboarding wave, your boards and reports look fine on the surface while ownership is quietly broken underneath.…

Hey I just baked a piece of code into a small app. What it does is: it lets Jira admins create custom select fields where each option has a description visible right in the dropdown. So instead of users guessing what "Level 1" or "Level 2" means, they see a short explanation below each option while browsing. Fully…

Hey Guys We're considering building this as a free Forge app. If there's enough interest from the community, we'll make it happen. Drop a like or comment if this would be useful for you. Already ran some analysis on this. No complexity, just an extra information layer on top of the dropdown options. Would require a new…

Hi Caterina, great App Jam Session, thanks again for your insight and pov on the asApp() vs asUser() topic. regarding the 401 i mentioned i sent you the exact endpoint in linkedin DM best regards c.faysal

I extended my research... This has been requested from Atlassian since 2017 (JRACLOUD-67882) and 2019 (JRACLOUD-79026). Still open.