Lenin Raj Atlassian Team

Hi @Maria Campbell - Please go to https://support.atlassian.com/contact/.

Hi @Maria Campbell, It could be that your git config is using a different email address than the one registered in Jira. If it is not the email address, please raise a support ticket and we can have a look.

Hi @Lisa Hooper, Bulk edit may be possible depending on how much different the values can be for each issue? Is it based on another field in the issue? If so, you can filter for that using JQL and use the 'Bulk Edit' option in the page.

Hi @Strong Based on the docs: https://developer.atlassian.com/bitbucket/api/2/reference/resource/repositories/%7Bworkspace%7D/%7Brepo_slug%7D/pipelines_config/variables/%7Bvariable_uuid%7D, you may need to include `uuid` and `secured` in the request body.

Hi @Victor Acin I am afraid this isn't possible. However to prevent someone from modifying the bitbucket-pipelines.yml file, you can use Branch Permissions, assuming your build/deployment runs from master branch. This will prevent anyone working on the repository to merge anything without approval.

Hi @N Apps You can use the `default-reviewers` API documented here: https://developer.atlassian.com/bitbucket/api/2/reference/resource/repositories/%7Bworkspace%7D/%7Brepo_slug%7D/default-reviewers

Hi @Brian Jennings, From your search results page, click on the "Google Sheet" icon: This will copy your results without "Issue Key".

Hi @Dharma Ramos Does your Smart TV has an option to enable "Request Desktop Site" (similar to what mobile browsers offer?

Hi @Brad Colvin I just tried status was "In Progress" BEFORE 2020-01-10 and it works for me: Also status was "In Progress" during (2020-01-05, 2020-01-10) works:

Hi @Michael Irving I believe this is possible using JQL. I have tested this and it seems to work. Step 1 - Create a JQL JQL: "Assigned Group" in (currentUser()) Add more filters you need Step 2 - Save this search as a filter Step 3 - Change the access of the filter appropriately so everyone that needs to access the new…

Hi @Geetha Ravi Your user might be missing write permissions for the branch you are pushing to. Eg. master. This can be checked from Repository settings -> Workflow -> Branch permissions.

I looked at previous questions for the same error and came across this answer: https://community.atlassian.com/t5/Jira-Software-questions/Local-installation-of-Jira-sofware-no-longer-functional-http/qaq-p/734713 Do you find any other errors in the log file?

Stranger Things

Hi @Steve Morse , Can you confirm if you are using the new issue view or the old issue view? If you can post a screenshot of your development panel and the commits dialog, it will be useful.