Marc -Devoteam- Community Champion

In the future, please create a new post when requesting this, as posting on resolved or historic topics is not the way to go. See this link to raise an issue in relation to an account, subscription or billing question to Atlassian

Hi @Areopagus Can.you share a screenshot of your user within admin.atlassian.com?

Hi @Sweta Shah On the rule (flow) details, what is the scope of the rule?

Hi @Sweta Shah What is the scope of the automation rule, is the correct space set and who can initiate the rule and the manual trigger?

Hi @Claudio Antonacci For my perspective what are you importing Jira issues or Test cases? Within using the Jira default importer, a summary is always required on each row. If you just want to import test cases with manual steps you should use the Xray Test Case importer Jira issue…

Hi @Claudio Antonacci Is this a test case and the above are all stepes within that test case? Is there no hidden row in your csv file or is the previous row missing a field or comma to specify that field to be empty? The issue will be in your csv.

HI @Danielle Cairns Can you elaborate more. Anyone can use smart links in Confluence, there is no need for admin rights. How would a Confluence function fit in poweroint?

Hi @Cecilia Pérez The Jira macro in Confluence is for showing Jira issue information on a Confluence space. This macro can't create issues. The macro settings can be adjusted to see what information for the found Jira issues can be shown, this is based on the fields used on the issue types on the Jira side. See the…

Hi @John Penna As @Arkadiusz Wroblewski is right on mentioning the feature request for this. On the layout of the issue, place the sprint field in the description section, this will provide you with a wider field perspective. This is related to the work item view, as the same complaints are noted, for fields like; * Parent…

Hi @Uwe Kühn Problem one, you have not whitelisted all IP related to Atlassian Cloud or, the reason for this is that JCMA has lost connection to your on-prem host. This is usually related that the connection has been terminated from the on-prem side, could be firewall ruling or some other restrictor on connection in your…

Hi @Benjamin Zhou If these steps in the workflow aare actual approval steps, then you coudl create a JQL filrer based on approval = pending(), this will show all work items waiting on approval, this filter you could use in a filter gadget on a dashboard.

Hi @Claudio Antonacci This is probably related to a misconfiguration in your CSV file. Can you provide file details (screenshots)?

Hi @Craig Duffy In short, ProForma forms is on or off, there is no option to enable this per project.

Hi @Cecilia Pérez Welcome to the community. ON Server/DC this is not an option as there is no Confluence automation , this is an exclusive CLoud feature. You would need to look at 3rd party marketplace solutions, see the options provided in other replies on your post.

Hi @Fabien Herelle Welcome to the community. As of today this is not possible yet, there is an open requets for this, CSM-64 

HI @Oleg Mastriukov I flagged this post for Atlassian Support. They will try to reach out to you via this post in 2 business days.

Hi @Chan_ Renee There are no options in the OCR for this, it can only read the attachment. It can't replace any information with the actual file.

Hi @Balakumar Your option would be to use a 3rd party app, to enrich reporting or dashboarding.

Hi @Elaine Beckford You would need a custom field, based on number type and then using automation rule and smart values store the number of hours into this field. See also this comunity…

Hi @Chan_ Renee Atlassian Rovo has OCR capabilities for individual image attachments, but it can't directly download, zip, or bulk export screenshot files from Jira tickets. Rovo only reads image text for analysis.

Hi @Florian Ehlig As @Gabriela - LeanZero mentions, this is certainly valid. Even Atlassian described this as a work-around in a feature request around this topic. https://jira.atlassian.com/browse/JRACLOUD-61024 

Hi @Serigne Could be but it's no logical and I won't implement such a solution. As providing such a solution it will be used. Work in my opinion, should happen from within JSM and the mailbox should not be access by users anymore

Hi @Daniel Sidler You need to go to the admin.atlassian.com. There under apps and sites select your site (prod), and in the new window under "service collection", "portal-only customers" you need to remove the customer

HI @Vaishali_Vashist Add the logo to the title, header or footer. Insert an image tag referencing a hosted image (e.g., an image attached directly to a Confluence page). Example snippet:<div class="fsTitlePage"> <img src="/download/attachments/YOUR_PAGE_ID/YOUR_LOGO_NAME.png" /> </div>

Hi @Oleg Mastriukov As I mentioned, if this instance is from a company, reach out to the IT department, they should no who manages the app in the organization.

HI @Serigne Why, would you want this. Agents should work from JSM tickets and their comments will be email to the customer who reported the ticket. If you work from an shared mailbox, why use an ITSM tool!

Hi @Nagaraju Welcome to the community. I assume you already have a statuspage, then see https://support.atlassian.com/jira-service-management-cloud/docs/manage-and-customize-your-status-pages/ 

Hi @Daniel Sidler The customer has to do the action of changing their email address on the Atlassian account they had. Now they have logged in again and a new account has been created, related to the new email address. So if the customer is still able to access the old account, then in the account settings the customer can…

Hi @Raja Singh Contact Atlassian Support for this. Here in community, most of us are Atlassian users like yourself, not (necessarily) employees of Atlassian. We don't have access to your environment. This community is an open public forum.

Hi @Balakumar This is normal behaviour. The issue has been in Sprint 2 and 3 and the isue now has status "Done". JQL finds the issue based on status, not based on status in a sprint. The sprint field shows in which sprint this issue has been in.