Default dashboard

Welcome to the Lucee JIRA issue tracking system.

As an open source project anyone is free to browse all the issues, current statuses, etc... If you register for a JIRA account you can then contribute to the project by adding new issue tickets, commenting on existing tickets or even taking on the development of a ticket.

We have configured JIRA with a relatively straight forward workflow with the following statuses:

• New - All issue tickets when first added will have a status of "new". This status means that they have yet to be triaged by a member of the Lucee Core Development team.
• Being triaged - Only a member of the Lucee Core Development team can triage a ticket and then either move it to "Awaiting Approval" or "Need more details"
• Need more details - More details are required from the original source of the ticket for the ticket to proceed further.
• Awaiting approval - This status means the ticket has been triaged and is now ready for the Lucee Core Development team to approve, reject or request more information on. If approved the ticket will move into the "backlog".
• Backlog - This status means a ticket is something that the Lucee Core Development team would like, at some point, to add to or fix in the Lucee core. Anyone can choose a ticket from this list and make the development and submit it for QA to the core development team.
• QA - This status means the development work is complete and the ticket now needs to be QA'ed and signed off.
• Ready to deploy - This status means the ticket has been developed and QA'ed and is ready to be merged into the Lucee core.
• Deployed - This status means the ticket has been merged into the core and published to a release version of the Lucee core.
• Rejected - This status means that the ticket has been rejected and a reason for it being rejected should, in most cases, be given in the comment(s) on the ticket.

We have set up this workflow so that there is a list of items, the backlog, that the Lucee core team have agreed upon, so that as a community member who would like to contribute to the core you know what we would like to be done. This of course does not stop you from doing a separate development to the core and submitting a pull request for your development if you like.

Would you like to join the Lucee core development team? Maybe you're a Lucee or CFML developer who would like to assist in triaging tickets, or a Java developer that is looking to dig in and improve Lucee? If so then we would be happy to hear from you. Please email andrew.dixon@mso.net with details of how you would like to assist and details of your relevant experience.