Oh, and it should have the option to exclude sub-tasks from Release Notes

Re: 2) Do you link the high level request to the development high-level task, i.e. to track when a client task has now been completed, and in which version? Manualy linking in Jira is very painful IMO.

1) JIRA pro allows sub-tasks.

2) Regarding tip#2; because JIRA doesn’t allow infinite levels of subtasks, it was suggested to me that we use a project that I now call “Requests” that store business-language requests in and a sister project called “Development” is used for the actual work to solve those requests. I name the projects “x requests” and “x development” (where x is your app name). Into the Requests project are things like “Make the application faster”. When the it is decided to have the dev team address the issue, like you said, many enhancements can be created to solve one request. I then use the sub-tasks to track things like acceptance tests for that particular enhancement, and documentation tasks to make sure help files and manuals are kept up to date (I can reconcile that each enhancement is documented). This approach does two things: 1- Allows users to request things in their own language and 2- keeps the development project “clean”. before we implemented this approach, we’d have hundreds, or thousands of unscheduled requests and that is depressing for development. Now the unscheduled requests are in the business owner’s project and it is up to them to prioritize.