Sandesh Shetty_fb9ccd Expert

@Mel Brooker Check browse project permission in service desk project permission schema. If external users have browse project permissions for other service desk projects, you have to remove it.

@iren lykhach You can check this https://community.atlassian.com/t5/Jira-questions/How-can-I-make-a-field-editable-only-for-some-role/qaq-p/934824

@Matteo Fattore You can't add request participant field to customer portal. JIRA Service Desk customer can still add Request Participant once the issue is created. To do that, user just need to create the request, click on "Share" then type the desired email address of the user that he wants to share the request. or You…

@Abiola Babajide I mean if you accidently deleted some ticket, then if you have taken backup earlier - you can restore those ticket by restoring process. But there is no stright forward option like restoring a deleted ticket.

@Abiola Babajide If you have backup, you can restore from the backup. It seems still we dont have any other option to restore the deleted ticket.

@[deleted] Refer this link https://confluence.atlassian.com/bitbucket/repository-tags-321860179.html#Repositorytags-CreateataginBitbucket You can create tag for a particular branch, you can see all commits in that tag. In your case you can create tag after you merging the pull request by selecting the branch which you are…

@Sejal Modi When you create a workflow it will be in inactive state because it was not associated with any project. When you add your workflow to one of the project's workflow schema, the state of workflow will changes to active because now it is associated with one project.

@Sejal Modi Associate inactive workflow with your project's workflow schema. for more info check this https://confluence.atlassian.com/adminjiracloud/managing-your-workflows-776636587.html

@Sejal Modi Use the workflow in some project. Select your project, click on workflow scheme and add the inactive workflow for the relevant issue types. This is how to replace the old workflow with the new one.

@Surat Jaemsri Its because 8443 is default https port. for more info refer this https://confluence.atlassian.com/doc/running-confluence-over-ssl-or-https-161203.html If you have changed the default https port, then you have to do this * Custom SSL port: If you have changed the port that the SSL connector is running on from…

@Pankaj Agrawal I think no other configuration is needed. Just make sure that -> go to your "project settings" -> screens -> in that screen those fields are available.

select your issue screen make sure that time tracking field is there, if not add that field

@Pankaj Agrawal where is my field option is available only for Jira admins. check on the "create issue screen schema" associated with your issue, make sure that time tracking field is available on that.

@Kirtik Rawal you should be the project admin to see this option. check the screenshots.

@Pankaj Agrawal Check on "where is my field" option https://confluence.atlassian.com/adminjiracloud/jira-admin-helper-818578850.html may be field is missing from specific screen

@Kirtik Rawal You can delete the project by going to Project settings -> Delete project. Make sure that if you are realy want to delete the project or just hide the project. To hide the project create a empty permission schema and associate that with that project. Please go throgh this link for more information:…

@Yanqun Le This is may be because of Firewall settings. Make sure that - firewall Inbound rule in 172.31.132.183 - the port 8088 is allowed to connect 172.31.132.173.

@Andrew Thanks for the post, I'm planning to take ACP-200 exam next month, can you please share the your experience on ACP-200? 

@Yanqun Le If you are connected to same network (network jira server connected to), you connect using IP address of server in which Jira server installed and port no. (eg. 192.168.x.x:8080)

@niit niit Check these links TAR.GZ https://www.atlassian.com/software/confluence/downloads/binary/atlassian-confluence-6.6.12.tar.gz Linux https://www.atlassian.com/software/confluence/downloads/binary/atlassian-confluence-6.6.12-x64.bin

https://confluence.atlassian.com/confkb/confluence-does-not-start-due-to-spring-application-context-has-not-been-set-218278311.html?_ga=2.58775789.1359027429.1555727745-666530993.1550497952 @Ken Ducey list in this article may be the reason check it once!

https://confluence.atlassian.com/servicedeskcloud/setting-up-service-desk-reports-732528965.html @Jason Gorman it may help you

@Raj This plugin may help you https://marketplace.atlassian.com/apps/43203/auditor-for-jira?hosting=server&tab=overview

Hi, We had simmilar problem, We solved in this way -> added default reviewer for PROD branch -> So before merging any pull request to PROD users should get the Approval from approvers. -> In your case if any user open a pull request from SIT to PROD, approvers can reject that Request. Refer this for more…

@Abelardo Aguiar You can add/remove field in create sceen of the issues. for more info refer configuring screen tab and field section in this url https://confluence.atlassian.com/adminjiraserver073/defining-a-screen-861253436.html

Is this works on Server version? or on cloud only?

Thank you @Josh Carolan

Thank you @Nic Brough -Adaptavist-

Thanks @Lime Trees

Thank you @Nic Brough -Adaptavist-