Android Q introduced a whole list of new features that provides a seamless user experience for users upgrading from Pie 9.0. Among them is a new feature called the Notification Assistant.

It is still work in progress (as of 13th May 2019, Q is still on Beta 3). If you're like me and use Hangouts, you will notice that you're not receiving any notifications from Hangouts messages sent to you. This doesn't happen with other messaging apps like WhatsApp, Telegram, SMS Messaging or Facebook Messenger.

After asking on Reddit, I've managed to resolve this issue on my Pixel 2 XL.

Image taken from Android Police.

Steps to Allow Notifications

1. Go to Settings > Apps & notifications
2. Then, tap on Notifications.
3. Under this section, disable the following options:
   • Automatic Notification Prioritizer
   • Hide silent notification status icons

After this, your Hangouts notification should appear whenever you receive any new messages.

Thanks to ysrzlkrnn for providing the tips to fix this.

The Error Messages

For some reason, you are attempting to update Ubuntu through the command line like so:

sudo apt-get upgrade

or via the Package Manager. But then you are getting the following errors (line 3 may be different for you, depending on the missing package):

W: Some index files failed to download. They have been ignored, or old ones used instead.
E: Malformed Status line, no 3rd word
E: Error occurred while processing libexiv2-11 (UsePackage3)
E: Problem with MergeList /var/lib/dpkg/status
E: The package lists or status file could not be parsed or opened.

or maybe this (line 5 may be different for you, depending on the missing package):

Reading package lists... Error!
E: Malformed Status line, no 3rd word
E: Error occurred while processing libexiv2-11 (UsePackage3)
E: Problem with MergeList /var/lib/dpkg/status
E: The package lists or status file could not be parsed or opened

These messages affirm that the APT repository is indeed broken.

Photo by Taduuda on Unsplash

Fixing the APT repository and Package Manager

First off, clean the APT list which may be corrupted:

sudo rm /var/lib/apt/lists/* -vf

Then, clean the Debian packaging modules:

sudo mv /var/lib/dpkg/status /var/lib/dpkg/status-bad

And replace the bad packaging module with the previous, working one:

sudo cp /var/lib/dpkg/status-old /var/lib/dpkg/status

Update the repository:

sudo apt-get update

By the end of this, your package manager and apt-repository should be fix and raring to go again!

Overview

We've written a post before on setting up Java on an Ubuntu or Debian box. It was a rather straightforward process, and easy to set up (as long as you follow the steps one at a time).

For Windows, the process is similar. For this guide, we'll be setting up the Java environment on the PATH system variable via the System Properties. In this guide, we'll be referring to Windows 10, but the same steps should work for other versions of Windows as well.

What You'll Need:

• Oracle Java JDK/JRE installed (latest version as of 5th June 2016 is Version 8 Update 91)
• Windows 7/8/10 or Windows Server 2008/2012

Configure Windows PATH System Variable for Java

1. First off, open up the System Properties window by: - right-clicking on This PC and selecting Properties

   you can also use the Windows key + Pause keyboard combo

   

2. Next, choose Advanced system settings:
   

3. Then, choose Environment Variables:
   

4. You will then see two sections: User variables and System variables. We're going to configure the Java executables to the PATH system variable.

5. Now, click on New under the System variables section (highlighted above). In the next screen that follow, add the following entry:
   

6. Click OK. The JAVA_HOME variable is now saved under the System variables section.

7. We're halfway there. Now, we're going to reference the JAVA_HOME variable with the Java executables. Under the list of System variables, look for the PATH variable, and then Edit:
   

8. You'll then be presented with a list of PATH values. These paths come from either installed applications, or ones that are set by Microsoft. When any directory gets passed here, only then their commands can be used in a command line interface. Click on New:
   

9. You'll be then prompted with an empty box for data input. Enter the following: %JAVA_HOME%bin
   

10. Click OK three times, until the Advanced system settings windows goes away.

11. Now you can test out the PATH system variable update for Java:

    Microsoft Windows [Version 10.0.10586]
    (c) 2015 Microsoft Corporation. All rights reserved.
    
    C:\Users\jusuc>java -version
    java version "1.8.0_91"
    Java(TM) SE Runtime Environment (build 1.8.0_91-b14)
    Java HotSpot(TM) 64-Bit Server VM (build 25.91-b14, mixed mode)
    

Pat yourself in the back! You've just configure Windows PATH System Variable for Java, and you can begin executing Java commands from the command line.

Extra Thoughts

As you may have noticed, we've used the %JAVA_HOME% environment variable to reference the location of the Java executables. By configuring this way, you can just simply update the %JAVA_HOME% without worries. Once done, you will then execute future updated Java commands from the command line.

Problem

If you attempt to clone a Bitbucket Server repository on SSH, you might stump into this problem:

D:\Documents\repos>git clone ssh://git@localhost/test/test-repo.git
Cloning into 'test-repo'...
ssh: connect to host localhost port 22: Connection refused
fatal: Could not read from remote repository.

Please make sure you have the correct access rights and the repository exists.

Cover Photo by Glenn Carstens-Peters on Unsplash

Explanation

Bitbucket Server listens for SSH connections on port 7999 by default.

Your users will need to include the port in the URL they use to clone from Bitbucket Server, for example:

git clone ssh://git@localhost:7999/test/test-repo.git`

Rather than have the port number in the URL, you may wish to set up port forwarding so that connections to the default SSH port are forwarded to the port Bitbucket Server is listening on (e.g. you could forward port 22 to port 7999).

This would allow your users to use a URL without a port number in it, like this:

git clone ssh://git@localhost/test/test-repo.git`

This simple how-to will guide you on how to port forward the SSH port on a Linux or Windows environment.

Solution for Linux

Atlassian provided a document on how to set up SSH port forwarding in Linux using HAProxy.

Solution for Windows

1. Open the command line prompt in Administrator’s mode and check if there are any existing routes that might interfere, using the command below:
   netsh interface portproxy show all
2. If no results are found, you can start to port forward the SSH port using the command below (you can identify Bitbucket's SSH port from here):

   netsh interface portproxy add v4tov4 listenport=22 connectport=   <BITBUCKET_SERVER_SSH_PORT> connectaddress=<BITBUCKET_SERVER_IP>
   

3. Run the same command as step 1 to check the results of your port forwarding:

   C:\WINDOWS\system32>netsh interface portproxy show all
   
   Listen on ipv4:             Connect to ipv4:
   
   Address         Port        Address         Port
   --------------- ----------  --------------- ----------
   *               22          localhost       7999
   

4. Attempt to clone your repository once more:

   D:\Documents\repos>git clone ssh://git@localhost/test/test-repo.git
   Cloning into 'test-repo'...
   The authenticity of host 'localhost (127.0.0.1)' can't be established.
   RSA key fingerprint is SHA256:jtrT+G9H9TPaZzcknnMsR8yJiK7PF0+xnYuNIxjRZuc.
   Are you sure you want to continue connecting (yes/no)? yes
   
   Warning: Permanently added 'localhost' (RSA) to the list of known hosts.
   
   Enter passphrase for key '/c/Users/jalex/.ssh/id_rsa':
   
   > warning: You appear to have cloned an empty repository.
   > Checking connectivity... done.
   

Mirror’s Edge is a game developed in 2009. For a game this old, you should not have any issues when playing it on modern day systems with the PhysX engine turned on. However, if you were to max out all the graphical settings and turn on PhysX, you will experience extreme lag and frame-drops. This quick guide will show you how to fix the extreme lag, and enjoy the PhysX module that comes with Mirror’s Edge.

The PhysX Problem

Mirror’s Edge comes with its own PhysX module files, but these files are outdated (back in 2009, mind you). Even though the latest PhysX modules are included in current nVidia drivers, the game will still use the older modules.

What you will see when you enable PhysX is the framerate drop when running through shattering glass:

The PhysX Fix

Note that this fix would only apply for machines with nVidia graphics card installed. If you’re using an AMD graphics card, skip to the next section.

Remember, always backup any directories before you start off any changes. This will allow you to rollback your changes in case anything goes wrong along the way.

What you can do to remedy this is to delete the following files from the Mirror’s Edge Binaries directory (from C:\Program Files (x86)\Steam\steamapps\common\mirrors edge\Binaries):

• PhysXLocal directory
• PhysXCore.dll
• PhysXDevice.dll

When you restart the game, you will notice no framerate drops but still experience the shattering glass and all PhysX have to offer!

When you delete the above files, the game will then utilise what is available in the system; which are the newer and more optimised PhysX modules that comes with the latest nVidia drivers.

What About Gamers with AMD Graphics Cards?

Unfortunately, the PhysX engine is only compatible with nVidia graphics cards. So, for those on AMD graphics cards, you should disable the PhysX option in the graphics options within the game.

You have a start date and an end date within an issue in Jira. On some cases, you may want to capture the elapsed number of days between those two dates (to calculate effort to complete the task, for example). This guide uses ScriptRunner to calculate the elapsed days between any two dates and add that value into a custom field. You can then use this field in any of your reports.

Cover photo by JESHOOTS.COM on Unsplash

Prerequisites

• Information from Jira
  • The Jira workflow to embed the script
  • The custom field name and its option IDs
  • The Date Fields to be used for comparisons
• ScriptRunner for Jira
• Groovy script to execute

Script to Calculate and Update Field with Difference between Two Dates

You can grab the script from my repository here: ValidateTwoDatesWorkflow.groovy @ Bitbucket

Configuration in Jira

In the workflow for the project, I added a new Custom Script post function to the Resolve Issue transition:

There could be an opportunity for you to automatically close issues after a certain period of time in Jira. You could always use the Bulk Update mechanism to bulk transition these issues, or you could let a Groovy script execute that for you automatically (after a set period of time). Here's a script on how you can achieve this on your Jira instance.

Cover Photo by Craig Whitehead on Unsplash

Prerequisites

• Information from Jira - Jira project(s)
• Transition ID from Done to Closed
• Username that is able to execute the transition to Close
• ScriptRunner for Jira

Script to Use

The script was from a Groovy ScriptRunner bug ticket raised a few years ago. Thanks, Marcel!

The script can be viewed on this page: close-issues.groovy @ Bitbucket

Where to make changes

// Global variables to be updated before utilising the script
int daysSinceResolved = 5 ; // days to check for issue closure
int actionId = 701; // transition id from Done to Closed
String project = "TEST, JIRA"; // target project key. To include more than 1 project, include the project keys in quotes
String previousStatus = "Done"; // status to check before closing
String username = "admin"; // acting user who has the privilege to transition issues to Closed
String comment = "Automatically closing issue since it has been resolved for ${daysSinceResolved} days.";

• daysSinceResolved: number of days to check for closing issues.
• actionId: the transition ID from the Done status to Closed
• project: the project key(s) to fetch the issues to close
• previousStatus: the name of the status to check before closing
• username: the username of the user who can execute the transition from Done to Closed
• comment: the comment to add once the transition to Closed is complete

Steps to Implement the Script

1. Upload the Groovy script to the $JIRA_HOME/scripts directory.
2. Ensure that the Groovy script is in 755 permissions, and owned by the user who starts JIRA:

   sudo chown jira:jira close-issues.groovy && chmod 755 close-issues.groovy
   

3. In JIRA, go to Administration > Advanced > Services.
4. Add a new Service, with the following information: - Name: an appropriate name for the service
   • Class: com.onresolve.jira.groovy.GroovyService
   • Schedule: Days per Week (Saturday and Sunday) and set the time to execute the service
5. Click Save.
6. Edit the newly created service to include the path of the Groovy script.
7. Click Update.

Jira doesn't come pre-build with information on who performed an action from the frontend. So, how can we find out who has updated a custom field that has impacted a lot of projects?

This is where the access logs come in, and Jira has this in the backend; running forever in the Tomcat Container.

Jira 6.1 and above already has an Audit Log feature built into the environment. This blog post may not apply to these versions of Jira, unless you want to go deeper into the access logs. Read more all about the Audit Log here: Auditing in Jira applications

Cover photo by Samuel Zeller on Unsplash

Find Out the Page that was Actioned Upon

So, let's say someone has added default values to a custom field; and this has impacted a lot of projects utilising this field. A project manager wanted to know who did this so that he can educate that user on the impact of his/her action.

For this example, let's say the affected field is the On hold reason field. Let's grab the URL when we choose to configure the field:

From the URL, deduce a unique identifier that distinguishes this custom field from the rest. Notice the red-boxed area in the screenshot above. Since we are finding a specific custom field change, grab the customfield_id:

&customFieldId=10323

Grab the Information from the Access Logs

1. We know the ID of the affected custom field, now let's find a list of users who has access this page before. Go to your $JIRA_INSTALL/logs directory and perform an ls -lah access*:

   ls -lah access*
   
   -rw-rw-r-- 1 ec2-user ec2-user 2.8M Nov  2 00:00 access_log.2014-11-01
   -rw-rw-r-- 1 ec2-user ec2-user 1.1M Nov  2 23:58 access_log.2014-11-02
   -rw-rw-r-- 1 ec2-user ec2-user  40M Nov  3 23:59 access_log.2014-11-03
   -rw-rw-r-- 1 ec2-user ec2-user  35M Nov  4 23:59 access_log.2014-11-04
   -rw-rw-r-- 1 ec2-user ec2-user  34M Nov  5 23:59 access_log.2014-11-05
   -rw-rw-r-- 1 ec2-user ec2-user  32M Nov  6 23:57 access_log.2014-11-06
   -rw-rw-r-- 1 ec2-user ec2-user  30M Nov  7 23:59 access_log.2014-11-07
   -rw-rw-r-- 1 ec2-user ec2-user 883K Nov  8 23:58 access_log.2014-11-08
   -rw-rw-r-- 1 ec2-user ec2-user 733K Nov  9 23:58 access_log.2014-11-09
   -rw-rw-r-- 1 ec2-user ec2-user  29M Nov 10 23:59 access_log.2014-11-10
   -rw-rw-r-- 1 ec2-user ec2-user  43M Nov 11 23:58 access_log.2014-11-11
   -rw-rw-r-- 1 ec2-user ec2-user  38M Nov 12 23:59 access_log.2014-11-12
   -rw-rw-r-- 1 ec2-user ec2-user  33M Nov 13 23:58 access_log.2014-11-13
   -rw-rw-r-- 1 ec2-user ec2-user  29M Nov 14 23:59 access_log.2014-11-14
   -rw-rw-r-- 1 ec2-user ec2-user 2.1M Nov 15 23:57 access_log.2014-11-15
   -rw-rw-r-- 1 ec2-user ec2-user 1.7M Nov 16 23:57 access_log.2014-11-16
   -rw-rw-r-- 1 ec2-user ec2-user  32M Nov 17 23:56 access_log.2014-11-17
   -rw-rw-r-- 1 ec2-user ec2-user  36M Nov 18 23:59 access_log.2014-11-18
   -rw-rw-r-- 1 ec2-user ec2-user  32M Nov 19 23:59 access_log.2014-11-19
   -rw-rw-r-- 1 ec2-user ec2-user  35M Nov 20 23:59 access_log.2014-11-20
   -rw-rw-r-- 1 ec2-user ec2-user  26M Nov 21 23:58 access_log.2014-11-21
   -rw-rw-r-- 1 ec2-user ec2-user 3.2M Nov 22 23:58 access_log.2014-11-22
   -rw-rw-r-- 1 ec2-user ec2-user 1.9M Nov 23 23:58 access_log.2014-11-23
   -rw-rw-r-- 1 ec2-user ec2-user  31M Nov 24 23:59 access_log.2014-11-24
   -rw-rw-r-- 1 ec2-user ec2-user  37M Nov 25 23:59 access_log.2014-11-25
   -rw-rw-r-- 1 ec2-user ec2-user  32M Nov 26 23:59 access_log.2014-11-26
   -rw-rw-r-- 1 ec2-user ec2-user  38M Nov 27 23:58 access_log.2014-11-27
   -rw-rw-r-- 1 ec2-user ec2-user  25M Nov 28 23:59 access_log.2014-11-28
   -rw-rw-r-- 1 ec2-user ec2-user 781K Nov 29 23:57 access_log.2014-11-29
   -rw-rw-r-- 1 ec2-user ec2-user 1.4M Nov 30 23:57 access_log.2014-11-30
   -rw-rw-r-- 1 ec2-user ec2-user  36M Dec  1 23:59 access_log.2014-12-01
   -rw-rw-r-- 1 ec2-user ec2-user  38M Dec  2 23:59 access_log.2014-12-02
   -rw-rw-r-- 1 ec2-user ec2-user  38M Dec  3 23:57 access_log.2014-12-03
   -rw-rw-r-- 1 ec2-user ec2-user  36M Dec  4 23:59 access_log.2014-12-04
   -rw-rw-r-- 1 ec2-user ec2-user  32M Dec  6 00:00 access_log.2014-12-05
   -rw-rw-r-- 1 ec2-user ec2-user 4.5M Dec  6 23:58 access_log.2014-12-06
   -rw-rw-r-- 1 ec2-user ec2-user 1.7M Dec  7 23:59 access_log.2014-12-07
   -rw-rw-r-- 1 ec2-user ec2-user  45M Dec  9 00:00 access_log.2014-12-08
   -rw-rw-r-- 1 ec2-user ec2-user  39M Dec 10 00:00 access_log.2014-12-09
   -rw-rw-r-- 1 ec2-user ec2-user  37M Dec 11 00:00 access_log.2014-12-10
   -rw-rw-r-- 1 ec2-user ec2-user  29M Dec 11 23:59 access_log.2014-12-11
   -rw-rw-r-- 1 ec2-user ec2-user  32M Dec 13 00:00 access_log.2014-12-12
   -rw-rw-r-- 1 ec2-user ec2-user 3.1M Dec 13 23:59 access_log.2014-12-13
   -rw-rw-r-- 1 ec2-user ec2-user 2.6M Dec 15 00:00 access_log.2014-12-14
   -rw-rw-r-- 1 ec2-user ec2-user  38M Dec 15 23:59 access_log.2014-12-15
   -rw-rw-r-- 1 ec2-user ec2-user  38M Dec 16 18:03 access_log.2014-12-16
   

2. From the command above, we found a lot of access_log files. Let's grep the above files for instances of the custom field that we are more interested in:

   less access* | grep '&customFieldId=10323'
   
   127.0.0.1 1340x3799190x1 tmahsun [14/Dec/2014:22:20:42 +1100] "GET /secure/admin/ManageConfigurationScheme!default.jspa?atl_token=B14E-GL73-6FKZ-OP3B%7C1969712ab02334ed26991c8ca7a02224b2252db9%7Clin&fieldConfigSchemeId=13913&customFieldId=10323&returnUrl=ConfigureCustomField%21default.jspa%3FcustomFieldId%3D10323 HTTP/1.1" 200 101259 485 "https://pinkie-jira.com.au/secure/admin/ConfigureCustomField!default.jspa?customFieldId=10323" "Mozilla/5.0 (compatible; MSIE 10.0; Windows NT 6.1; WOW64; Trident/7.0)" "flt8wy"
   127.0.0.1 1340x3799191x1 - [14/Dec/2014:22:20:42 +1100] "GET /s/d41d8cd98f00b204e9800998ecf8427e/en_US135a92-1988229788/6262/55/ebda7fb1e8929bc87f332ce20a1ecfe0/_/download/contextbatch/js/atl.admin/batch.js?cache=false&isAdmin=true&supportedApplication=true HTTP/1.1" 200 6840 5 "https://pinkie-jira.com.au/secure/admin/ManageConfigurationScheme!default.jspa?atl_token=B14E-GL73-6FKZ-OP3B%7C1969712ab02334ed26991c8ca7a02224b2252db9%7Clin&fieldConfigSchemeId=13913&customFieldId=10323&returnUrl=ConfigureCustomField%21default.jspa%3FcustomFieldId%3D10323" "Mozilla/5.0 (compatible; MSIE 10.0; Windows NT 6.1; WOW64; Trident/7.0)" "flt8wy"
   ...
   

3. We can assume that the user tmahsun has perform edits in the custom field's default value, but that might not be the case. You may encounter a lot of lines from the command above, and that may exceed the limit of the terminal's buffer; so we may miss out a lot of other potential users as well. Let's output the command above to a file instead to grab all the information for investigation:

   less access* | grep '&customFieldId=10323' > cf-access
   

4. Now if we were to less the file cf-access file, we can narrow down the users who has accessed this page:

   less cf-access
   
   127.0.0.1 1340x3799190x1 tmahsun [14/Dec/2014:22:20:42 +1100] "GET /secure/admin/ManageConfigurationScheme!default.jspa?atl_token=B14E-GL73-6FKZ-OP3B%7C1969712ab02334ed26991c8ca7a02224b2252db9%7Clin&fieldConfigSchemeId=13913&customFieldId=10323&returnUrl=ConfigureCustomField%21default.jspa%3FcustomFieldId%3D10323 HTTP/1.1" 200 101259 485 "https://pinkie-jira.com.au/secure/admin/ConfigureCustomField!default.jspa?customFieldId=10323" "Mozilla/5.0 (compatible; MSIE 10.0; Windows NT 6.1; WOW64; Trident/7.0)" "flt8wy"
   ...
   127.0.0.1 813x3906269x1 sysadmin [16/Dec/2014:13:33:51 +1100] "GET /secure/admin/ConfigureCustomField!default.jspa?customFieldId=10323 HTTP/1.1" 200 47363 438 "https://pinkie-jira.com.au/secure/admin/EditCustomFieldDefaults!default.jspa?atl_token=B14E-GL73-6FKZ-OP3B%7C193d84aec30b4d9394e50b40923c29a944b7af5a%7Clin&fieldConfigSchemeId=13913&fieldConfigId=15413&customFieldId=10323&returnUrl=ConfigureCustomField%21default.jspa%3FcustomFieldId%3D10323" "Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/39.0.2171.95 Safari/537.36" "pb0gye"
   

5. Only with the cf-access file can we drill down who has updated the custom field's default value, and we can safely say that username tmahsun is the user we're after (only if we are the sysadmin user that updated the field based on the project manager's request).

Final Words

With the above method, we can deduce almost all users' activities within a Jira instance. The only steps you have to do is:

1. Find the distinguishable identifier from the affected page's URL.
2. grep the logs for this information.

If you ever browse to a project's settings to change the notification scheme, you might bump into a stack trace; resulting in you to not being able to change the notification scheme for that project, or other projects that share this same notification scheme. This guide will show you how to resolve this issue.

Cover photo by chyneyee. See more of her work here: Redbubble

Stack Trace

Cause:
java.lang.IllegalArgumentException: Custom field with id 'customfield_10034' does not exist.
Stack Trace: [hide]
java.lang.IllegalArgumentException: Custom field with id 'customfield_10034' does not exist.
at com.atlassian.jira.issue.fields.DefaultFieldManager.getCustomField(DefaultFieldManager.java:674)
at com.atlassian.jira.notification.type.UserCFValue.getArgumentDisplay(UserCFValue.java:196)
at com.atlassian.jira.projectconfig.contextproviders.ProjectNotificationContextProvider.getNotifications(ProjectNotificationContextProvider.java:179)
at com.atlassian.jira.projectconfig.contextproviders.ProjectNotificationContextProvider.getContextMap(ProjectNotificationContextProvider.java:102)
at com.atlassian.jira.plugin.webfragment.CacheableContextProviderDecorator.initContextMap(CacheableContextProviderDecorator.java:70)
at com.atlassian.jira.plugin.webfragment.CacheableContextProviderDecorator.getContextMap(CacheableContextProviderDecorator.java:46)
at com.atlassian.plugin.web.descriptors.DefaultWebPanelModuleDescriptor$ContextAwareWebPanel.getHtml(DefaultWebPanelModuleDescriptor.java:143)
at com.atlassian.jira.projectconfig.tab.WebPanelTab.getTab(WebPanelTab.java:75)
at com.atlassian.jira.projectconfig.servlet.PanelServlet.outputTab(PanelServlet.java:163)
at com.atlassian.jira.projectconfig.servlet.PanelServlet.doGet(PanelServlet.java:136)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:617)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
at com.atlassian.plugin.servlet.DelegatingPluginServlet.service(DelegatingPluginServlet.java:42)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
at com.atlassian.plugin.servlet.ServletModuleContainerServlet.service(ServletModuleContainerServlet.java:52)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
...

Do note that customfield_10034 is the ID of the problematic custom field. It could be any value apart from 10034.

Possible Cause(s)

One of the most probable occurrence of this issue is when you are migrating your Jira instance from one location to the next, but do not have the specific custom field in the new instance yet. In natural cases, it is possible to specify a custom field to the notification scheme (an example of this is when you would like to notify a group of users based on the custom field itself).

Resolution(s)

1. Find whether the custom field really is missing (via the database):

   select * from customfield where id = 10034;
   

   If the result came out to zero, then the custom field is indeed missing:

   id | customfieldtypekey | customfieldsearcherkey | cfname | description | defaultvalue | fieldtype | project | issuetype
   ----+--------------------+------------------------+--------+-------------+--------------+-----------+---------+-----------
   (0 rows)
   

2. Find related notifications referring to the said custom field:

   select * from notification where notif_parameter = 'customfield_10034';
   

   This query would return a lot of notifications types:

   id   | scheme | event | event_type_id | template_id |       notif_type        |  notif_parameter
   -------+--------+-------+---------------+-------------+-------------------------+-------------------
   10051 |  10000 |       |             2 |             | User_Custom_Field_Value | customfield_10034
   10052 |  10000 |       |             3 |             | User_Custom_Field_Value | customfield_10034
   10053 |  10000 |       |             4 |             | User_Custom_Field_Value | customfield_10034
   10050 |  10000 |       |             1 |             | User_Custom_Field_Value | customfield_10034
   10054 |  10000 |       |             5 |             | User_Custom_Field_Value | customfield_10034
   10055 |  10000 |       |             6 |             | User_Custom_Field_Value | customfield_10034
   10057 |  10000 |       |             7 |             | User_Custom_Field_Value | customfield_10034
   10056 |  10000 |       |            14 |             | User_Custom_Field_Value | customfield_10034
   10058 |  10000 |       |             8 |             | User_Custom_Field_Value | customfield_10034
   10059 |  10000 |       |             9 |             | User_Custom_Field_Value | customfield_10034
   10061 |  10000 |       |            11 |             | User_Custom_Field_Value | customfield_10034
   10060 |  10000 |       |            10 |             | User_Custom_Field_Value | customfield_10034
   10063 |  10000 |       |            15 |             | User_Custom_Field_Value | customfield_10034
   10062 |  10000 |       |            12 |             | User_Custom_Field_Value | customfield_10034
   10065 |  10000 |       |            13 |             | User_Custom_Field_Value | customfield_10034
   10064 |  10000 |       |            16 |             | User_Custom_Field_Value | customfield_10034
   10263 |  10021 |       |             3 |             | User_Custom_Field_Value | customfield_10034
   10265 |  10021 |       |             2 |             | User_Custom_Field_Value | customfield_10034
   10268 |  10021 |       |            14 |             | User_Custom_Field_Value | customfield_10034
   10274 |  10021 |       |            12 |             | User_Custom_Field_Value | customfield_10034
   10269 |  10021 |       |             7 |             | User_Custom_Field_Value | customfield_10034
   10262 |  10021 |       |             1 |             | User_Custom_Field_Value | customfield_10034
   10272 |  10021 |       |            10 |             | User_Custom_Field_Value | customfield_10034
   10267 |  10021 |       |             5 |             | User_Custom_Field_Value | customfield_10034
   10266 |  10021 |       |             6 |             | User_Custom_Field_Value | customfield_10034
   10276 |  10021 |       |            16 |             | User_Custom_Field_Value | customfield_10034
   10271 |  10021 |       |             9 |             | User_Custom_Field_Value | customfield_10034
   10277 |  10021 |       |            13 |             | User_Custom_Field_Value | customfield_10034
   10273 |  10021 |       |            11 |             | User_Custom_Field_Value | customfield_10034
   10275 |  10021 |       |            15 |             | User_Custom_Field_Value | customfield_10034
   10264 |  10021 |       |             4 |             | User_Custom_Field_Value | customfield_10034
   10270 |  10021 |       |             8 |             | User_Custom_Field_Value | customfield_10034
   11006 |  10021 |       |            17 |             | User_Custom_Field_Value | customfield_10034
   11031 |  10000 |       |            17 |             | User_Custom_Field_Value | customfield_10034
   (34 rows)
   

3. Confirm which notification schemes are these notifications attached to. Use the values in the scheme column in the previous SQL query:

   select * from notificationscheme where id = 10000 OR id = 10021;
   

   You'll get a list of notification schemes:

   id   |                   name                    | description
   -------+-------------------------------------------+-------------
   10000 | Default Notification Scheme               |
   10021 | [LS] AIRlog - Default Notification Scheme |
   (2 rows)
   

4. Delete notifications with the problematic custom field:

   DELETE from notification where notif_parameter = 'customfield_10034';
   

5. Restart Jira.

A typical installation of Ubuntu comes prepacked with the OpenJDK environment. This environment is substantially enough for regular users who wish to develop simple Java programs. However, some Java libraries are not included or compatible with the OpenJDK environment. Take Atlassian Jira as an example of an application that requires the more traditional and proprietary Sun Java JDK platform. Due to its proprietary status, Ubuntu does not include this in its repository. Hence, we would need to install this manually.

Despite the title, this guide has also been tested in a Fedora, Debian and CentOS environment. If it doesn't work for you, let me know by leaving a comment below! :)

Cover photo by Caspar Rubin on Unsplash

Check Operating System Type

First things first, check whether you’re running on 32-bit or 64-bit Ubuntu:

uname -m

The result will show you what type of operating system you have:

• i686 – 32-bit kernel
• x86_64 – 64-bit kernel

Instructions

Initial setup

Now, go to the Oracle JDK download site and decide which version of JDK you would prefer.

In this guide, we'll be downloading Java JDK 8 Update 162. Accept the agreement, and copy the tar.gz link for your operating system type.

We'll use wget to download the compressed file. In your terminal, type the following:

wget --no-cookies --no-check-certificate --header "Cookie: gpw_e24=http%3A%2F%2Fwww.oracle.com%2F; oraclelicense=accept-securebackup-cookie" "http://download.oracle.com/otn-pub/java/jdk/8u162-b12/0da788060d494f5095bf8624735fa2f1/jdk-8u162-linux-x64.tar.gz"

The cookie header is included in the wget command because Oracle does not allow a direct download without accepting their agreement; thus, we parse a cookie to ensure that Oracle recognises that you have accepted their agreement.

Create a new directory under opt:

sudo mkdir /opt/java

Then, extract the compressed file to the above directory:

sudo tar -xzvf jdk-8u162-linux-x64.tar.gz -C /opt/java/

Verify that the files are extracted correctly:

cd /opt/java

ll

total 12K
drwxr-xr-x 3 root root 4.0K Jan 10 05:16 .
drwxr-xr-x 3 root root 4.0K Jan 10 05:12 ..
drwxr-xr-x 8 uucp  143 4.0K Sep  6 02:32 jdk1.8.0_162

Now, we’ll create a symbolic link called current and link it with the newly extracted JDK directory:

sudo ln -s jdk1.8.0_162/ current

ll

total 12
drwxr-xr-x 3 root root 4096 Jan 10 05:20 ./
drwxr-xr-x 3 root root 4096 Jan 10 05:12 ../
lrwxrwxrwx 1 root root   12 Jan 10 05:20 current -> jdk1.8.0_162/
drwxr-xr-x 8 uucp  143 4096 Sep  6 02:32 jdk1.8.0_162/

Set Environment Variables and Path

Finally, we’re going to set the $JAVA_HOME environment variable so that you’ll be able to run most Java applications.

To set for a single user:

Let’s load the .bash_profile from the home directory:

nano ~/.profile

Go to the end of the file, and add the following:

export JAVA_HOME=/opt/java/current
export PATH=$PATH:$JAVA_HOME/bin

Hit Ctrl and x to save the file, and y to overwrite it.

Finally, to ensure the changes are instant, run the following command:

source ~/.profile

To set for all users:

This step is similar to the above, with the only exception being that you would need to edit the global profile file. This allows every user the right to understand the environment variable that was set.

The global profile file can be found in the /etc/ directory. You'll need to use the sudo command to make changes to this file.

Verification

Once it's all completed, run the java -version command to verify the correct Java version and type:

java -version

java version "1.8.0_162"
Java(TM) SE Runtime Environment (build 1.8.0_162-b12)
Java HotSpot(TM) 64-Bit Server VM (build 25.162-b12, mixed mode)