Yogesh Mude_u145qk Expert

HI @Kitti Bihari In this case, I guess the customer need licence right ? Not required. I don't want to let him to browse all projects or all organizations, only that one which is his company. Yes, then create new permission scheme for the project and then associate to the project. Add the customers to Service Desk…

Hi @Kitti Bihari I don't want the other customers to see eachothers issues at the oranization. Just add the reporter in Browse project permission, so that only the reporter can see their own tickets.

HI @Shrikant Maheshwari If you have been configured Outgoing mail then only you will get an email for recover password. You can find the SEN number https://my.atlassian.com site. Please have a look at the below article for retrieving password.…

Hi @Manu Mishra Here is the same question has been created by one of the User, please have a look at it.. I don't this so it will be possible, you need to write your own custom JQL function add-on.

Hi @Swetha Nyayapati Welcome to the community! For restricting the user to view project, the steps as follows... 1. Create role/group for that project, add the users into it. 2. Create permission scheme and add those role/groups into Browse project permission. 3. Associate the permission scheme with the project. So only…

HI @dworm Please have a look at the below community questions, hope it helps.. https://community.atlassian.com/t5/Sourcetree-questions/Getting-quot-fatal-Authentication-failed-for-quot-error/qaq-p/624663 https://community.atlassian.com/t5/Sourcetree-questions/SourceTree-quot-fatal-Authentication-failed-for-quot/qaq-p/201844

HI @DJM If you are creating repo with git init then we can consider this repo as working directories and if we are creating repo with git init --bare then wa can consider this repo as bare repo but the difference is structure.

HI @Manu Mishra I think this can not be done currently, you can find already created feature requests as below... https://jira.atlassian.com/browse/JRASERVER-27539 https://jira.atlassian.com/browse/JRASERVER-22506 Or else you need to your own custom JQL function add-on.…

I am glad to hear is your issue has been solved. If you feel this answer have been helped you to solve the issue then please don't hesitate to accept this answer, this will help others those who will face the same issue in future.

In this case, you need to work either of these ways.. 1. You need to work with the custom script post function using Script runner ....while creating issue check the user role/group and then assign it to respective managers. 2. using component. 3. Manually user needs to assign issue with their respective managers while…

Yes, to change/configuring/associating permission scheme with the project you need to have project admin or Jira admin rights. do i need to delete the global group i have created at the beginning? Actually, i don't know for which group are you talking about but I suggest you don't delete anything just un-associate it.…

Thanks for the detail description....in this case, the default jira post functions will not work like I and @Ollie Guan has been mentioned earlier. Let me ask you one more time is all the three manages follows the same process or different (process workflows)?

HI @Emmanuel Montes Welcome to the community! To manage global permission for all the users, Create a group/role and then create a generic permission scheme in which give the appropriate rights(Create issue, Edit Issue, Delete Issue, Manage Sprints and so on) to the group/role. Associate this permission scheme to the…

HI @YFS Jira Admin Welcome, to the community! The steps is as follows... 1. Go to Admin --> issues --> Workflow create a new workflow with four statuses that you want to use. 2. Create a new workflow scheme and add this newly created workflow to this scheme. 3. Associate the workflow scheme to the projects in which you…

HI @Duong Pham Welcome to the community! Adding to @Nic Brough -Adaptavist- answers just to have a look at the below issue. It's related to changing base URL for cloud instances. https://community.atlassian.com/t5/Jira-Service-Desk-questions/Changing-Base-URL-of-cloud-JIRA-Service-Desk/qaq-p/820345#M16324

Hi @Stephen Farrell Welcome to the Community! It could happen when this email address is in the bounce list to Atlassian. This happens so your mail service doesn't lower Atlassian's emails reputation, which could degrade the quality of service of JIRA Cloud. So please try to contact Atlassian Cloud support they will help…

Ok, let me ask you users manager is one entity or multiple? If one then you can achieve with the Update issue field post function.

HI @Pradeep T Welcome to the community! If you are talking about the single user manager then you can use the Update issue field post function and just you need to select Field as an Assignee and provide the field value as respective user manager.

HI @Christina Donegan To update the workflow across all the projects...copy the existing workflow which was currently using and add the two statuses that you wanna add and then associate this copied workflow to workflow scheme. Apply this workflow scheme to the projects. Please have a look at the below article for the…

HI @sudhakar yala Can you please check the git checkout local documentation using below command.. man git-checkout

HI @Frank Dombrowsky Currently, JSD will support only below fields while editing issue during automation. * Assignee * Component/s * Labels * Linked issues * Priority * Description * Summary * Environment * Due Date Here is the feature request has been raised for the same to allowing the other fields like label, custom…

HI @Martin Cerny Actually, we can not control on basis of issue type in Jira. permission scheme will apply for all the issue type. I don't think so this will be possible. As reference documents were given by @Mark Markov which is related to issue security level but not the restricting to create/edit/delete issue in jira.…

HI @HelixTech7 Is this options are properly showing to your PM when he/she logged into Jira.

HI @Aman Garg Welcome to the community! Please have a look at the below article for integrating Jira and Jenkins. https://docs.marvelution.org/display/JJI/Jenkins+Integration+for+Jira https://community.atlassian.com/t5/Bitbucket-questions/Bitbucket-Server-integration-with-jenkins/qaq-p/307023 As you mentioned in your…

HI @shruthi sj Can you please attach the screenshot and check whether the reporter has create issue permission for that specific project.

HI @sudhakar yala I am glad that I helped you to solve your problem. For more details please have a look at the below article.…

HI @sudhakar yala Its Ok, X branch is remote branch correct? can you please use the below command and check. git checkout --track origin/X

HI @sudhakar yala As you are using [root@ululin033 devlabsctl]# git checkout ci...but this ci is not listed in branch list.

It should switch from any branch to any. Is this X branch is created from bitbucket using create branch or git? If this X branch is created from Bitbucket server then can you please try to create a new branch using below command from git and try to switch in between. git checkout -b <branch_name>

HI @ashok 1234 Please find the below articles. https://confluence.atlassian.com/jirakb/export-more-than-1000-issues-to-excel-from-issue-navigator-in-jira-cloud-779160811.html https://confluence.atlassian.com/jirakb/exporting-a-filter-result-containing-more-than-1000-issues-191500982.html