Page Comparison

...

What follows is a summary of the (start!) of the work we see ahead, and a broad plan for how we will approach this.  It's informal and does not form a guarantee any particular feature will be implemented within any particular time frame - we get spiked by some activities such as building out full integration testing and releasing JEMH DataCenter with Marketplace licensing support in 2018.

Profile to Project Mapping feature migration (

...

JEMH-5404

...

)

JEMH is moving slowly toward the JEMHC Project-Mapping centric model:

Responsibility Devolution (

...

JEMH-5403

...

)

Currently JEMHC is only manageable by JIRA System Administrators.  This was historically because one Profile could impact many projects, and exposing the ability for one user to break other projects configurations was not acceptable.  With more configuration being moved into Project-centric Project Mappings, we plan to create Project Admin configurable settings for JEMH, that expose the specific Project Mappings from all Profiles (including the Default Project Mapping) that can then be locally administered by Project Admins.

As part of this work, many other areas of JEMH also need devolution for Project Centric views:

• Subject blacklisting

• Attachment blacklisting

• Auditing 

...

• 

• Template Sets

• Test Cases 

...

• 

• Event Listener

• Static Resource 

...

As part of enabling devolved administration, we also need to implement some new features, specifically Auditing of configuration changes for tractability.

Currently we exposes read-only views of the Event Listener configuration for the given project.

UI Redesign in 3.0.0

As monitors have got wider, heading into Jira 8, we plan JEMH 3 to have a new UI, using a vertical nav to maximize vertical screen space, this will allow more vert nav licenses to be injected without loose screen height.

Work Plan

We will need to balance two main paths of work:

...

b) Responsibility Devolution

Backlog