What do you dislike about SpiraTeam?
Requirements is listed under "Planning". I could not find them at first use.
The non-standard custom report templates do not allow complex queries. I want to be able to execute SQL queries with joins, for example to list associations between requirements and test cases.
The custom reports do not allow to set the header and footer sections of MS Word reports. I cannot generate reports in the style that is prescribed by our company governance process.
The number of standard item types is too limited. I would like to be able to add explanatory text blocks to my requirements, so that I can generate complete reports in company style. Also, I want to be able to structure requirements in chapters, but without the chapter titles being requirements as well.
For a first draft of a requirements document, I want to be able to renumber the requirement IDs. For non-tech people, it is difficult to read documents that have non-contiguous numbering.
I want to be able to layer requirements, so that I can manage all requirements in a single project, but still be able to generate MRS, SRS, PRS, HRS, SWRS, etc. documents.
I want to be able to store and re-use "company-standard" requirements. That way I only need to specify deviations when I have a new project.
The two views on the requirements list are cumbersome to work with Why not combine them into a single view, like JAMA Contour does? Review collected by and hosted on G2.com.