|
History
| Log In
|
|
|
|
We had to implement this (along with Component/s) as custom fields in order for multiple projects to search.
That way we lost the ability to "manage" the versions, and also compromise on the individuality of the drop down values of the projects. Just presenting the system 'Component/s' and the 'affects/fix version' fields and allow for a text search would help a bit. Sorry guys, i still do not understand the suggested Solution to the Problem - would you be so kind and explain it to me again?
@Jean: - i don't understand what you mean by "Just presenting the system 'Component/s' and the 'affects/fix version' fields and allow for a text search would help a bit.":
@Scott - waht do you mean by "just hide the system 'project' field"? Where/how can i achieve this and would it have an effect on other JIRA-Functions? I'm looking for a new Solution which would not cut off already useful JIRA-Features... Hi Alexander,
If you select a single project, Component/s and the Version/s-related fields are presented in filtering as a drop-down lists with the value in the list as defined for that project. If selecting 2+ projects, then these fields are not presented for filtering anymore. May be it's difficult to present a list of combined values from all projects in scope? I am not sure if making them availabile as text search, like how summary or description can be searched, would be an easy fix? Thanks, My company would benefit from the ability to select multiple fields and have all custom fields display/searchable/queriable if there is different content in the dropdown of each project, just include them ALL.?
This has been a big issue for us as we have to run each project separately and then pull them into one excel. Not pretty! Our company needs the same kind of flexibility in making filters.
We would like to run filters to see what issues are logged on component's with the same version number cross multiple projects . It would be very useful to search by version. The reason for this is that there maybe multiple issues for multiple projects on the same version. It is quite handy to see all the versions in one filter.
A possible extension on this idea would be a higher level ('enterprise') release version...
Ie when there are multiple projects (ie data conversion, projects for shared libraries, various other projects hanginig off) that will be released together that follow either the same or different version numbering/release dates etc, but generally need to be tested together, having an 'enterprise level Version' to gather up all the versions of the 'sub projects' that go with this overall version could be handy? And the ability (if you have the right permissions) to query over the 'Enterprise' level version, and create road maps, and release note (with sub-road maps/release notes etc for each project in that version). I work on various 'enterprise' projects where there are diff versions of the db and code, and it can be hard to work out which go together (and impact of changes in one on the other). Being able to wrap them up into one search etc at the higher level could be rather useful. bit of a lengthy explination on that one sorry! |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
 |
|
New Feature
Open
Critical
Ability to filter/view Issues upon "Versions" across multiple "Projects"
You can do this currently if you wish, and just hide the system 'project' field.
Would that work for you?