Ensure a job name is set before being able to use navbar

This is an odd thing where if a job is created without a name, the
navbar will then become enabled, despite the UI theoretically not
allowing this behaviour. This code now just adds the requirement to
always have a job name be set.
Merge branch 'master' into bug/acm-DSC-515
Changes to Parent PI rules.
Add ignore for intellij
stop users spamming the check button.
Merge branch 'master' into js-bugfix
extra links on home page of banjo

Signed-off-by: mossrocket <peter@mossrocket.com>
Merge branch 'master' of https://github.com/nla/banjo
Fix for reports table overflow

Full screen width used for container

Signed-off-by: mossrocket <peter@mossrocket.com>
Up amberdb version to 151
Revert "Ensure a job name is set before being able to use navbar"

This reverts commit 7331908a3d37246507697a78edfd46c3a9592586.
Merge pull request #588 from nla/bug/acm-DSC-373

Move amberdb to v151 for DSC-373 plus add some intellij stuff to gitignore
Ensure a job name is set before being able to use navbar

This is an odd thing where if a job is created without a name, the
navbar will then become enabled, despite the UI theoretically not
allowing this behaviour. This code now just adds the requirement to
always have a job name be set.
Updated rule for Parent PI for DSC-465
Merge branch 'master' of https://github.com/nla/banjo
Merge branch 'master' into ti_parent_pi_rule_change
Change if/else conditions into switch.
Merge pull request #586 from nla/js-bugfix

Js bugfix
Merge pull request #587 from nla/cat-report-fix

Fix for reports table overflow
Merge pull request #589 from nla/bug/acm-DSC-515

Ensure a job name is set before being able to use navbar