|
[
Permlink
| « Hide
]
Wangjammer 5 added a comment - 14/Nov/05 05:00 AM
This is a really good idea. Issue linking definitely needs to be made more useful and more user friendly.
This should be relatively easy to do now with issue operations being pluggable (
We should look into adding an example of this in the toolkit so people could easily customise. This would be extremely useful to us if we could specify multiple projects, components and versions. Our biggest problem in JIRA right now is how to assign a new or existing issue to multiple projects and their respective versions. We have a number of applications/products which share a significant common library. These products are tracked as separate JIRA projects. When an issue is reported by QA or a customer they associate that issue with the product and have no clue as to wether it is at the application level or common library level. So issue gets reported against the current product under test.
However, if this issue really occurs down in the common library then we must manually clone and then move it to several projects in order to track the issue separately in products that might have different versions and different release schedules. This is tedious. We thought of having a Common Library project, but this still would require alot of overhead as issues were constantly moved between the JIRA projects for the product and the common library. If this feature could target multiple projects, components and versions, then we could simply create one issue and then click Create Linked Issues and specify a list of project/component/versions in one step. This would be an absolutely fantastic feature for which there's currently no good workaround. Hate to do this, but I need to reschedule. 3.5 is jam packed and we are hoping to release in few weaks.
This would be most helpful if the issue could be dirctly created in a different project then the issue which it is being created from. For example of one the weakness of CLONE, is that if want to clone the issue into a different project you have to create the clone and them move. Please dont let the enhancement suggested by this issue fall into that same trap.
This one feature would greatly enhance acceptance in our company - we really want to tie all issues to their requirement issue - so a single click option like this would save much time.
We want to use JIRA as a requirements management tool. Since subtasks only allow one level of nesting (and because we want to link in things like test cases and the like) we need to use the linking capability to tie requirements together. Unfortunately, right now that's a cumbersome process that includes trying to remember what issue number you want to link from. This is a high priority feature for us.
I am a new Jira user, and have actually been tasked with configuring Jira as our company's change control tracking system for auditing purposes. (Jira is already being used by development). Linking issues as described here would allow other departments to handle their own issues and then simply link to a new change control project for my department to implement. I anticipate this addition.
This would be a fantastic feature - it would allow us to kick off other minor tasks in a different project that are linked to a main project. This is far more elegant than creating the other minor tasks, then finding each of them to create links after the fact.
I agree this would be very useful. I frequently find myself creating related issues and I have to go back and remember to link it after it's created.
Anyone managed to accomplish this by a workflow transition?
i am exploring this option, if i could only find a linking post function Someone appears to be starting work on a plugin to do this:
http://confluence.atlassian.com/display/JIRAEXT/Create+and+Link |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
 |
|
New Feature
Open
Major
Create a Linked Issue operation
