Comments
-
Hi @Shuoyu Hu JSM don't have feature like you described out of the box. You need to search additional app that will provide you this. In the past I used: - https://marketplace.atlassian.com/apps/4832/enterprise-mail-handler-for-jira-jemh?hosting=cloud&tab=overview…
-
Did you check cloud migrator from Atlassian? https://support.atlassian.com/migration/docs/perform-a-cloud-to-cloud-migration-for-jira/ Regards, Seba
-
Hi @Peter Wåhlin It shouldn't be an issue with this. Does your project permissions allows to modify reporter? Regards, Seba
-
HI @Shubham Burghate Can you tell more about this export&import? Is it from jira cloud to jira cloud or other configuration? Regards, Seba
-
Hi @Neeta Dubey Project is on the same instance? If yes, create new project and move tickets. Regards, Seba
-
Hi @murali kadiri You can use behaviour but with this you can't hide whole transition screen. What you can do is to hide several fields on screen and leave default comment field on a screen (comment screen is always displayed) and make field visible and mandatory when component will be ABC. Regards, Seba
-
Hi @flim Unfortunately it is not possible in JSM. From project you can grant/restrict access to all request types. I don't know if it possible by app from marketplace. Regards, Seba
-
Hi @jira.admin IPESOFT From what version did you upgrade to 7.19.16? Did you check upgrades notes? Did you copy all changes from old version into new one? Regards, Seba
-
Hi @Lisa Zanini Please contact with add-on vendor to confirm if Automation for Jira is working with it. I didn't find anything that app is compatible with Automations actions. Regards, Seba
-
Hi @venkatesh_goteti As I understand - while you edit a document page was deleted or just your data on edit mode was gone? Regards, Seba
-
HI @Myleen Van Es What is your need? Based on screenshot JQL is wrong (too much ANDs). IMHO it should be created>= and created <= OR created>= and created <= Regards, Seba
-
Hi @Mkrtich Tono Please check if on transition from$Resolved to $Closed there is no condition/validator that can block it. Looks like issue with that. Regards, Seba
-
Hi @itsubscriptions.om Regarding migration from server to cloud please take a look here - https://www.atlassian.com/migration/plan/cloud-guide#requirements Atlassian provide tool and support team which can helps you. Regards, Seba
-
I know! Chris told me :D
-
Hi @Vaasugi Velmurugu Please contact with Atlassian support (https://support.atlassian.com). Looks like issue with bitbucket. Regards, Seba
-
Hi @Saranya Did you try to review your rules and optimise it like Atlassian advise here - https://community.atlassian.com/t5/Automation-articles/Introducing-our-new-packaging-model-for-Jira-Cloud-Automation/ba-p/2446099 ? Regards, Seba
-
Hi! It is possible. Reporting in Time to SLA: https://appfire.atlassian.net/wiki/spaces/TTSC/pages/35946564/SLA+Reports+Overview Unfortunately, I didn't find any docs from SLA Powerbox to send it to you.
-
Hi @Mario Nikolov Below apps that I used in the past to have SLA: - https://marketplace.atlassian.com/apps/1211843/time-to-sla?hosting=cloud&tab=overview - https://marketplace.atlassian.com/apps/1215330/sla-powerbox-on-time-service-delivery?hosting=cloud&tab=overview IMO those are the best and I was very happy about them.…
-
Hi @V MALLIKARJUNA Below few tutorials how to do this. - https://ddevops.com/postgresql-upgrade-from-version-9-5-to-version-12/ - https://www.shernet.com/postgresql/upgrading-to-postgresql-10-on-centos-7/ There is a lot of pages with steps. Regards, Seba
-
Hi @francisco.pineda IMHO best option will be do this via REST API - https://docs.atlassian.com/software/jira/docs/api/REST/1000.824.0/#api/2/user-removeUser Regards, Seba
-
Hi @Naresh Gantala Did you check JSM built-in reports? What metrics you want to present in reports? Regards, Seba
-
Hi @Kannpitcha Paponphatsiri ! Please check this answer - https://community.atlassian.com/t5/Jira-questions/ERROR-quot-message-quot-quot-Client-must-be-authenticated-to/qaq-p/1076087 Looks like you need to add header or switch to api tokens. Regards, Seba
-
Hi @Aaron P_ I'm afraid it is not possible. You can clear whole label field by post function. IMO you can use automation rules where it is possible. Did you consider it? Regards, Seba
-
Hi @Brendan Sheppard I'm not sure if capital letters make difference but can you try to use {{initiator.accountId}} ? Also what I see is that after }} there is a dot. Please remove it. Regards, Seba
-
Hi @Sandesh TM Did you consider Automation for jira functionalities? Regards, Seba
-
Please ask Atlassian support about that. I don't have idea why it works like you said
-
Hi @Sriram Prabu Can you explain what is deployment environment? Is it a custom field?
-
If you want to limit list of statuses you need to change status names in request forms. More info you can find here - https://support.atlassian.com/jira-service-management-cloud/docs/customize-the-workflow-statuses-for-a-request-type/ Regards, Seba
-
Hi @Nirose I don't know solution for that. I'm afraid that on marketplace there isn't something like you need. Regards, Seba
-
hi @Zoë Floyd ! No, if you will change a name all links will work because inside url's you have space key. Even if you decide change space key links will work too. Confluence will remember old space key and redirect to new link. Regards, Seba