Himanshu Tiwary_go407r Rising Star

Hi @Li_ Suhan , Your saved filter is correctly limiting the issues shown, but the gadget’s dropdowns are generated from fields the gadget can actually recognize and aggregate. That is why standard fields like Issue Type, Status, Updated, and Reporter appear, while your Bitbucket Project, Bitbucket Repository, and Bitbucket…

Hi @adssadasd , this looks like a local environment or install issue rather than a problem with rovodev run itself. The key part is that the bundled executable is failing to load NumPy’s C extensions, which usually points to a broken or incomplete CLI/plugin install on the machine. Since it is running from the Atlassian…

Hi @a40 , you should still be able to contact Atlassian Support even without the Rovo Dev webspace URL. Just mention that the webspace is never created, so no URL is available, and include your Atlassian site URL, the exact error message, and the Trace ID Since it has been failing consistently for a week, this still looks…

Hi @Vaclav Pechr, If the Responsible team is your own custom field, then yes, your use case is really about being able to use that field more flexibly in SLA goal conditions, so that the SLA or OLA can reflect how long the issue stayed with each team during the workflow. From what I can confirm, Jira Service Management…

Hi @Chris Edris What you’re trying to do makes sense, but the part that’s fighting you is {{destinationIssue.issueLinks}} because it returns a collection, and JQL is not great at cleanly filtering that inside the rule. A simpler and more reliable approach is to let automation do the walking for you instead of trying to…

Hi @Hardik Sharma Plans in Jira are basically used for big-picture planning. They help teams look across multiple projects and answer things like: what are we delivering, when will it happen, what depends on what, and do we have the capacity for it? The main thing to know is that Plans is the newer name for Advanced…

H @Andre T_ i, For something specific to ConfiForms, it is usually better to open a separate ticket directly with the ConfiForms team rather than wait here. Community posts can sometimes be seen by vendors or other users, but there is no guarantee that someone from the app team will pick it up quickly. So if you want a…

Hi @Andre T_ , Thanks, that changes the picture a lot. If this is a ConfiForms feature, then I would not treat it as a standard Confluence Cloud limitation anymore. In that case, if it worked before in Cloud and now the values disappear after saving, it is much more likely to be either a ConfiForms-side issue, a recent app…

 For sure, and also if you find it helpful can you please give me a recognition in my profile as it will help me a lot :)

Hi @Andre T_ , This sounds more like a limitation in Confluence Cloud than a bug. In Cloud, access is usually controlled at the space, page, or database level, not at the individual field level, so if you are trying to restrict one field to only certain users, Confluence may simply not support that setup. That would…

Hi @dvaughn , Yes, you can do this to a point in Confluence by linking items between databases, so one project can be connected to risks, benefits, teams, or other records in separate databases. The limitation is that Confluence does not work as deeply as Notion for multi-database relationships and reporting. So you can…

Hi @Derek Fields _RightStar_ , That’s a fair clarification, and I agree the situation becomes much more difficult without a proper backup. My main point was that this should not be treated as a normal reinstall or simple rollback. Once Jira has been started on the higher version, you cannot just put the older binaries back…

Hi @Alexandre Godin , This usually looks more like a configuration or permissions issue than something you are doing wrong in the widget itself. If the Object Type dropdown is empty even though the schema clearly has object types, the first things I would check are whether you actually have access to those object types in…

Hi @Richard A_ Michaels , From everything that’s publicly available, I wouldn’t say DX Service Cloud is replacing Compass, and I haven’t seen any official announcement that Compass is being sunset. Atlassian still has Compass listed as an active product, with current documentation and ongoing updates, which normally would…

Hi @Tony Montana , In most cases, you can’t just install Jira ITSM 10.3.18 over 10.7.4 and expect it to work correctly. Once 10.7.4 has updated the database and home data, going back to 10.3.18 is usually not a simple downgrade. The proper way to fix it is to restore your database, Jira home, and install files from backups…

Hi @ARVIN KUMAR , he single most useful one for this case is this Atlassian doc on project permissions and roles: https://support.atlassian.com/jira-software-cloud/docs/understand-project-permissions-and-roles/ A kudos is appreciated :)

Hi @Chris Edris , I think the main issue is that your rule is a bit too broad once it starts branching through linked tickets. The trigger itself makes sense, but when you use “For linked work items,” Jira will go through all linked issues on the Dev ticket, and at that point it does not clearly distinguish between the…

Hi @ARVIN KUMAR , Yes, this can definitely be done, but usually not through a standard Jira board alone. A board is mainly designed for the teams doing the day-to-day work. If you want a leadership-level view that shows the overall business picture, key risks, and financial benefits, while still allowing Jira users to work…

Hi @James Rizk, Thanks for the extra detail. If you’re using Easy Exporter and the JQL part is not working properly inside the export, the easiest workaround is usually to run the JQL in Jira first, save it as a filter if needed, and then export from the Issue Navigator results. In many cases, that works more reliably than…

Hi @Matteo Pacenti , From what I know, this can’t currently be enforced. The template will load when users create an idea from inside Jira Product Discovery itself, but not when they use the general Create button from Jira. So unfortunately, if people are creating tickets from the standard Jira create screen, the JPD…

Hi @a40 , This looks more like an Atlassian-side issue than something you’re doing wrong. The biggest clue is that you’re getting a Trace ID with the error. Usually that means the request is reaching Atlassian’s backend, but something is failing on their side when the Rovo Dev webspace is being created. make sure Rovo Dev…

Hi @Ambrose Qiu , This is most likely not a Golang issue, but a Bitbucket test reporting behavior. Bitbucket Pipelines only shows test results when your build generates a JUnit XML report in a supported folder such as test-results or test-reports. So for Go, it’s not enough to just run go test — you usually need to convert…

Hi @Reece Meyer , You’re not missing anything here this is a current limitation of the Assist / JSM app for Microsoft Teams, rather than something you’ve configured incorrectly. At the moment, JSM Forms aren’t fully supported in Teams via Assist, which is why you’re only seeing some custom fields and not the actual form…

Hi @Vaclav Pechr , As far as I can confirm, it is not possible to utilize Response team in SLA setup in Jira Service Management Cloud in the current setup. Moreover, I did not find any information in current Atlassian documentation that SLA editor v1 in Cloud supports this. Atlassian documentation regarding current SLA…

@Arkadiusz Wroblewski If there's a chance to get please get me M size too😹

Hahaha, I guess that's the atlassian joke for the day :P and ironically is very importance and a time saving convection for a atlassian admin to work in a instance so versatile

Exactly, We have so much customisation in the in app even the automation makes it a quick process

Hey @everyone, it’s March already. Is anyone still here? Drop a like to mark your attendance. :P

Hi Victor, You can use different email domains for email requests in JSM, as long as that mailbox is reachable and supported by the email channel setup. Atlassian supports using a custom email address for receiving requests. That said, the error “SOCKS: Host unreachable” usually points to a connectivity issue to the mail…