What feature do you want most in JWM in 2024?

[Jason S]

Happy 2024!

With most of us now settling back into work for the year, what better time than now to share with us what you want out of JWM this year.

What features or changes do you want to see in JWM in 2024?

Big or small, it doesn’t matter - let us know in the comments below. We take into account feedback and data from a variety of sources, so your input here could help tip the scales towards the feature you’ve been wanting to see!

Jason and the JWM team

[Mo]

• More choice around approvals. e.g. multiple approvers, only one required to progress.
• The ability to decide when a task is auto removed from the completed boards
• One final one (though this is probably just Jira in general) - regarding custom fields - if a custom field has 10k values (the limit I believe), why send all 10k values to the browser and hinder the users performance? Now one answer to this might be to not use too many values, but what about when the option is a customer, supplier or item and we want data accuracy over a free typed field? We shouldn't have to look to add-ons to do something that should be built in (lazy loading)

[Matthew Canham]

I've been using automations to notify when an issue is due. I would love if due date notifications came out of the box with a new project so I don't have to set up an automation every time.

[Jason S]

I'll start: Customised charts and reporting to get the insights that are most relevant to my stakeholders

[John Funk]

Mine is probably very much the same as @Mohammed Ibrahim  - but specifically, the ability to implement try Approvals like what JSM has where it is built in to the Workflow process, has the ability to Approve issues by email without logging in, the ability to add custom fields to the notice emailed to Approvers, etc. 

Second would be the ability to add multiple boards to a JWM project. This basically amounts to the ability to add JWM projects to the Location field when creating a board. That way I can see all of my issues on a single board and not be stuck with different views based on workflows. 

Both of these are assuming after getting the nesting problem fixed and deployed for Timelines.  And basically, fixing all of the open JAC tickets.  :-)

[Jason S]

Thank you, @Mohammed Ibrahim !