Nikola Perisic Community Champion

Hey @Arun , Not with Forge, only with the Postman. And this was actually for the cloud. So, you are using int for the server?

Hi @Ward Schwillens_ Schwillie , Issue keys in Jira cannot be changed. Since this needs to be in the ascending order, you should be using a JQL query for this instead. BR, Nikola

Hi @Peter Gottstein , Check the console (Inspect -> Console) and see if there are any errors showing, like status codes that are either in range of 400 (client) or 500 (server). If this doesn't help, I'd suggest to use a different app. BR, Nikola

Also, are you adding it as a header image or attaching it as a regular image on the page?

Hello @Wendy G , I am curious if this is happening for all of the pictures or only for the one that you have designed? BR, Nikola

Hello @Shuchi Shah , The expiration time for the Xray Cloud REST API token is 24 hours from the moment it’s generated. You can find the reference here: https://docs.getxray.app/display/ProductKB/%5BXray+Cloud%5D+How+to+use+REST+API+with+Xray+for+Jira+Cloud

Hello @Jonathan Hildebrand , Sometimes in the cloud when not receiving the emails despite all of the verified checks, Atlassian may for some reason black listed the email addresses. If nothing works that Fabio has mentioned, raise a support ticket for Atlassian about this issue. BR, Nikola

Just to clarify: are you using the "Jira Issues" or the "Jira Legacy" macro - legacy is outdated?

Is it like, the quality of the picture gets worse?

Interesting, I will have look into these add-ons, can you post their names?

Hey @Arun In the logs I see the 403 forbidden access. Not sure why is this showing to you. Also another thing You need to fill out these required fields (expand the arrows for required fields). Another strange thing is that it isn't asking for an API key, so how does it know where to create the dashboard. Have you tried…

Hello @Shan Hoffmann , Have you tried using a different browser?

Hey @Arun , Yes, after the deployment, you need to use forge install command. From there you need to enter your Jira instance website. Tip: When you need to make the frequent changes in the app, use the forge tunnel command, which will update your app with every change that you make in your code.

Hello @Heather Millar , Have you signed up to the waiting list? Users who did sign up, get access to this feature earlier than others. You can sign up here: https://www.atlassian.com/software/confluence/databases BR, Nikola

Hello @nzalotti , By versions, do you mean on the features that are being released? Or perhaps the UI? Because, yes, some videos might have a different interface than the one you are using, since the UI is being updated along with the features that are being rolled out. Do you have a specific issue? BR, Nikola

Hello @Amir Noseri The blue part of the progress bar is when the issue is in the "Progress" status category. The green part of the progress bar is when the issue is in the "Done" status category.

Hello @Erik , Is the workflow having a condition that might be affecting that specific user? BR, Nikola

Hello @Prathima , by file do you mean an attachment that needs to be moved to a different page?

Hello @tfetner , Do you get any error message when you try to insert the confluence macro for jira?

Hello @Krish.loku , An alternative would be to create the automation that will have the trigger "Issue created" followed by the action of "Edit issue" for "Description" field which will have the additional {{issue.key}}. Now, to be able to reference the issue key when typing, currently is not possible.

Hey @Arun Yeah for Forge apps, you need to add some additional permissions and scopes Now for Confluence, all of the scopes you can find on this page: https://developer.atlassian.com/platform/forge/manifest-reference/scopes-product-confluence/

Hi Carsten, This sounds like a bug from the Atlassian side. If the issue still persists, contact the Support.

Hello @Arun , Since you are using a forge app to access the API, within your manifest.yml file you need to add the scope and permissions: Then you will prompted from to accept the access. When you deploy, you would need to update the changes that have been made.

Hi @Bushra Ansari , Check with your site admin about this, make sure that the IP allowlisting is having your IP in there as well. Also, check with them to make sure that you were not removed from the site (which is another possibility).

Hello @Bushra Ansari , Few possible reasons: 1. You were removed from this instance - possibly by the admin 2. Your credentials (possibly password) were changed Can you send the error message that you are receiving? BR, Nikola

I believe this can help: https://support.microsoft.com/en-us/office/saving-doc-to-docx-or-dorm-0107099d-dc1e-4897-8851-f8c9f483f7cd#:~:text=Open%20the%20document%20%3E%20Navigate%20to,as%20type%E2%80%9D%20%3E%20Select%20Save.

Export the issues from Business project and then import them in the Software project. As for when it should be developed, it needs to be manually created.

Hello @Katherine Todd , this change would be possible to audit if you have the audit log option enabled. It is strange that the accounts got deactivated like that. I would suggest to contact the Atlassian support. BR, Nikola

For this I would set up an automation that would transfer stories automatically to done status once when the subtasks are completed. 

Heya @Arun , You can do this by using the Jira API for dashboards. It has Forge code for dashboards as well. You can find it here: https://developer.atlassian.com/cloud/jira/platform/rest/v3/api-group-dashboards/#api-group-dashboards Cheers, Nikola