Tuncay Senturk _Snapbytes_ Community Champion

Hello @Pedro Webster There is no bundled option for that, but you are free to use a free app on the Marketplace. You can check SnapMetrics - Real Time Analytics, which has an Issue History Report that allows you to list the changes in that field. I am one of the team members; feel free to ask questions if you need further…

That endpoint is not officially documented, and the 404 error can occur when the export job has not yet finished. The backend creates an export job asynchronously, so you need to wait for it to complete. Another reason for receiving a 404 might be an invalid resourceId. If you are still confident that everything is correct…

Ok, assuming there is nothing wrong in the atlassian-jira.log file, let's make sure that your atlassian-plugin.xml file includes the below line <spring context="component-scan"/> Then go to manage Apps > your plugin > plugin components and ensure that IssueCreateEventListener is listed and enabled there. If not listed, the…

Hi, I am not saying the build errors; it's the atlassian-jira.log file where you can find the logs related to the plugin initilization and associated errors. Reviewing this log file will help a lot.

Hi, Don't use the <component-scan> in plugin-context.xml with the Atlassian Spring scanner together. They are alternatives, sorry if I was misunderstood. So, remove the context:component-scan from the plugin-context.xml file. In your pom.xml add these dependencies <dependencies> <dependency>…

Hi @George Nistor The listener code seems structurally correct. If onIssueEvent is not being triggered, and as far as I see you use annotation-based scanning, you need to ensure that it's being scanned correctly. Check that the class is part of a package under the scanned component-scan base package, in spring-scanner…

Hi @Abhijeet Sonawane I haven't implemented a fully working solution yet, but you can automate daily exports of Assets data by using the internal export API, downloading the ZIP, and uploading it to S3. Although not officially documented or supported (afaik), some teams use this sort of solution in their production…

Hi @Integrations Sorry for the late response but it is better to ask this kind of questions to https://community.developer.atlassian.com/ to get more answers. Forge CLI does not support logging in using admin API tokens, even if the token has the right scopes. Forge CLI expects a full user authentication session, not a…

Hi @Ronald Lam Take a look at this article by Atlassian; it outlines the steps to recalculate SLA data by calling a REST function. (rest/servicedesk/1/servicedesk/sla/admin/task/destructive/reconstruct?force=true)

Yes, most possibly the JPMC internal network is blocking access to Atlassian Cloud. I'd suggest raising a request to the network/firewall team to allow outbound access to Jira Cloud. This is the site that you need access Host: globalshares.atlassian.net Protocol: HTTPS (port 443) They will either fix it in the Firewall…

Hi @Athul Abraham I am not sure if you've already solved the problem. It seems to be a network related timeout, not a Jira specific error. The IP 13.227.213.4 is an AWS IP used by Atlassian and your internal network may be blocking outbound access to this Atlassian Cloud server. You can allow outbound https traffic to the…

Hi @Admin Welcome to the Community! Just a quick note, this is the Atlassian Community, a public forum where users help each other. No one from Atlassian will contact you directly by phone or email from here. I recommend deleting your private information. If you need direct assistance from Atlassian Support, you'll need to…

Hi @[deleted] If I get it right, yes, there is a way to better manage this than hardcoding every name in the automation tab. An option is to use Jira Assets. Create an object schema in Assets (e.g. Team Directory), and add an object type (e.g. Team Member) with attributes: Name (John Doe), Team (Service Desk) Create an…

Hi @joel.geller Unfortuntaley, you have to use an app to achieve that. If you are open to using a free app, you can view any issue field change by using the Issue History Report of the SnapMetrics - Real Time Analytic app, which is available on the Marketplace. You can see every change along with the date, time, and user…

Hi @Saad Ahmad If you are open to using a free app, you can achieve everything with the SnapMetrics - Real Time Analytic app available on the Marketplace. You can easily set Time in Status or Transition Date/User metric and view the results through your preferred filters. Trust me, you will enjoy it once you start using it…

Hi @Armelia McCord There is no built-in feature in Jira to directly clone a child work item within an Epic. However, you can achieve this by navigating to the Issue Navigator and using the JQL query: parentEpic = <epic-key>. From there, you can clone any of the child work items by clicking the three-dot menu next to the…

Nope, afaik they haven't resolved the ticket yet.

Hi @Bakong_Servicedesk I recommend raising a support ticket directly with Atlassian.

Hi @Aidan Satterwhite Yes, that's one of the frustrating issues. I used to use {code} or {noformat} macros to preserve the leading spaces: {noformat} after the spaces {noformat} It's annoying to add these macros just to keep spaces, but I haven't a clue if there's a more reliable way to fix this.

Hi @Giuseppe Torraco Welcome to the Community! Please take this with a pinch of salt. Rovo does not have direct access to the JSM SLA APIs, because Atlassian has not exposed SLA data through public REST APIs in a usable or supported way for third-party apps or external agents like Rovo. But I believe, Rovo can retrieve SLA…

Hi @Ahmed Omar In order to understand the root cause, let's check a couple of items first. First go to Dashboards > View all dashboards. The dashboard might still exist but it may no longer be marked as your favourite or shared. If it was deleted, unfortunately, jira doesn’t support a way to restore deleted dashboards.…

Hi @Vitheya Monikha The reason you're not getting projectId in the context data is because the context is global (isGlobalContext: true). It is not bound to any specific project, so projectId is not present. To get projectId included in the context data, you need to create a custom field context scoped to a specific…

I'm glad that it's resolved :) 

Hi @Gregg Reaves I've heard similar issues recently, I believe you're not alone. It seems there might be a bug but it is not confirmed as an incident yet (as far as I know). I'd recommend asking the users to try using a different browser or switching to private/incognito mode. If that doesn't help (or in both case) it…

Hi @Vitheya Monikha I am not sure if I get your question right but here are my two cents on this. To set the scope of a custom field to a specific project using your Forge backend function, you need to create (or find if there is) field context that is scoped to the project, and then add the option to that context. const…

Hi @Amy Martin afaik, Jira 10.x (based on Java 17 and its tightened security) no longer supports third-party Groovy libraries like HttpBuilder or RestClient, so you're now limited to native Java/Groovy HTTP clients. As I said, I am unsure though. To handle NTLM authentication with native Groovy or Java classes…

Thanks for clarifying, that's helpful. Jira automatically enables clustering if it detects a cluster.properties file. Let's rename or delete the cluster.properties file from the Jira home directory. Then stopping jira and, deleting dbconfig.xml, cluster.properties files and caches/indexes folder may be a good idea before…

Hi @Vhee Van I suppose, you're running Jira Data Center with clustering enabled by default, and since this is a new setup, Jira expects cluster-related configuration files(nodes config). However, accessing via <a href="http://localhost:8080" target="_blank" rel="nofollow noopener noreferrer">http://localhost:8080</a>…

@Michael Wohlgemuth is absolutely right. There are too many points that need to be identified. Is it a JSM request or a raw HTTP/API request? If the error mentions unsupported content or a failure to create an issue, it’s really important to check the Jira application logs (at atlassian-jira.log). The logs often provide…

Hmm, I'm not sure but it is worth trying to only render when value is defined. Could you try the below updated code? import React, { useState, useEffect, useCallback } from "react"; import ForgeReconciler, { Textfield } from "@forge/react"; import { CustomFieldEdit } from "@forge/react/jira"; import { view } from…