Mikael Sandberg Community Champion

Security Scheme allows you to control which issues users and/or groups can see. Have a look at the documentation for it, https://confluence.atlassian.com/adminjiracloud/configuring-issue-level-security-776636711.html

Checkout this thread, https://community.atlassian.com/t5/Bitbucket-questions/SourceTree-2-1-10-0-Authentication-Issues/qaq..., about authentication issues in the new version of SourceTree. Hopefully that will help.

If it is on the screen it will only be displayed if it has a value.

I don't think you can do it in core JQL, but if you have JQL Tricks (on JIRA Server) you could search for all issues that have epics corresponding to a specific JQL, like this: issue in issuesWhereEpicIn("project = \"PHA\"")

You need to include $REPO as well, $FILE only includes the path within the repository. This worked for me when I tested it right now Btw, the "inappropriate language or spam" is a known issue and it is being worked on, see https://community.atlassian.com/t5/Feedback-Forum-articles/Known-issue-HTML-markup-errors/ba-p/625791

Database Custom Field can be used to extract data from a csv file, https://confluence.cprime.io/display/SIL/CSV+Files+Data

Are you able to log on to my.atlassian.com? Also, make sure that IE is not blocking JavaScripts.

According to the error code it looks like the account you are using has been disabled, https://confluence.atlassian.com/stashkb/ldap-error-code-49-317195698.html

Since you are mentioning "multi license" I assume you are using version < 1.8.x and want to upgrade from that. SourceTree changed their license model as of 1.8.x and are now using Atlassian account instead of a license file, so there is no way of getting rid of that popup window. Here is a blog post from back in the days…

Did you try changing the filter? This filter should do it for you: project = X AND issuetype != Sub-task ORDER BY Rank ASC This is what it would look like: The board on the left is showing all issues, including sub-tasks, and the one on the right is using the query above to exclude sub-tasks.

Guess I need to read the question a bit better... Missed the part about giving read only users access to it. Unfortunaltely I don't have the answer, but you may want to see if you can find a request, or file one, to have that fuctionality added to Bitbucket Server. Usually Bitbucket Server will get most of the things that…

The latest version of Bitbucket Server has the ability to edit files directly on the server. I am running 5.3.0 in my test environment and it has an Edit button when you look at the source. It has been available since 4.13, here is the blog post about it.

Does the Time Tracking field exist on the Create/Edit screen? If not then you need to add it to that screen and also the Default one in order to see it.

It might be related to this known issue, https://community.atlassian.com/t5/Feedback-Forum-articles/Known-issue-HTML-markup-errors/ba-p/625791

Have you added the "Deploy Time" field to the screen used to view issues? Sounds like it has only been added to the screen for create/edit.

Are there any resent changes to the plugins that you are using? If you put JIRA in safe mode, does that make any changes? If a plugin has changed right around the time emails stopped working than I would contact the vendor for that plugin so they can investigate what is going on. 

If you have admin permissions on the board you can change the filter query being used to exclude issues that are closed.

The screen configuration is under JIRA Administration > Issues > Screens. If you are using multiple screens in the project, it might be easier to look under the Project configuration and see which Screen is being used when you Create an issue. You should also check and see if the field configuration is being shared with…

Are you JIRA Cloud or JIRA Server? And if JIRA Server, what version are you on? From what I have found so far, the Epics option is only available on JIRA Cloud.

You need to either own the board or be one of the admins for the board. Whoever created the board for you should be able to either modify the filter or give you admin rights to it. Here is the link to the documentation on how to create a board, which also describe how to modify the filter…

Do you have admin permission in JIRA? In order to change the screen/field configurations you need admin rights, so if you do not have it you should check with your JIRA admin and see if they made changes to the field configuration.

Do you have the field Technical Specifications on the screen? It looks like it is set as required in the Field configuration for the project, so you need to either add the field to the screen or make the field optional.

Checkout this thread, https://community.atlassian.com/t5/Bitbucket-questions/SourceTree-2-1-10-0-Authentication-Issues/qaq-p/623202, about authentication issues in the new version of SourceTree. Hopefully that will help.

Under Board > configure you can change the filter query that is being used for the board to exclude subtasks.

Are all projects using the same notification scheme? Have you checked it to see if anything has changed in it?

Yes, your user accounts in Confluence are managed via JIRA. I have the same setup, and would recommend that you check the sync from time to time. On a couple of occations the sync between Confluenc and JIRA has failed, and I have had to create a copy of the user directory to get it working again.

Go to User Directories under Confluence administration > Users & Security. You can have multiple directories, and when you create users it will created in the first one that is writable. This is what I have in my test environment. The first directory is controlled by JIRA. You can also check which directory a user belongs…

Are your users controlled by an internal Confluence user directory or an external user directory? It sounds like you are using an external user directory if you do not see Set Password, Delete, and Disable.

I don't think you can change the behavior of the Log Selected option, but you should be able to create a custom action that uses the --follow option.

You could use a query to get the existing tickets and then do a bulk edit on them to set the value for the custom field.