History | Log In     View a printable version of the current page.  
Issue Details (XML | Word | Printable)

Key: JRA-1140
Type: New Feature New Feature
Status: Resolved Resolved
Resolution: Duplicate
Priority: Major Major
Assignee: Mike Cannon-Brookes [Atlassian]
Reporter: Jonathan Nolen [Atlassian]
Votes: 8
Watchers: 2
Operations

If you were logged in you would be able to see more operations.
JIRA

Versions that Cross Projects

Created: 16/Jan/03 01:27 PM   Updated: 20/Oct/05 09:47 PM
Component/s: Filtering & Indexing
Affects Version/s: 1.4.3
Fix Version/s: None

Time Tracking:
Not Specified

Issue Links:
Duplicate
 
Reference

Participants: Jonathan Nolen [Atlassian], Mike Cannon-Brookes [Atlassian] and Timur Evdokimov
Since last comment: 275 weeks, 6 days ago
Resolution Date: 20/Oct/05 09:47 PM
Labels:


 Description  « Hide
> I also have a question about issue filtering: We're running
> multiple development projects. We're using an XP methodology,
> which schedules development in small chunks, called iterations.
> So Project ABC and XYZ both have a version called "Iteration-10,"
> and it represents the same two weeks of development.
>
> We would like to be able to filter by "All Projects" and by
> version "Iteration-10," and thus show us every task we need to
> accomplish in this two week iteration, regardless of which
> project it is in. This is not possible now, so far as I can see.
> Is there anyway to make this happen, either now or in 2.0?

Right - hrm, file a feature request on jira.atlassian.com for it. It's a little tricky to do with the current architecture (as two components with the same name really have nothing to do with each other in the data model), I'll have to think about how to do it.



 All   Comments   Work Log   Change History      Sort Order: Ascending order - Click to sort in descending order
Timur Evdokimov - 29/Jan/03 09:58 AM
Just my EUR 0.02

The software model of our company (we do solutions for warehouse logictics) implies customized solutions based on the same core. The application consists of core module, custom logics module and maybe a couple of other supplementary modules.

When a release is done, the version of custom logics module defines release version. But core and all those supplementary modules have got their own versioning. Therefore, I would like to see in JIRA a link between different versions of different modules. Perhaps just in the same way JIRA links issues to each other.