Vote #78106
未完了Custom field: issue linking
0%
説明
I desperately need the custom field for issue lining.
Example: I have one tracker named "Customers". Another tracker called "Jobs" (currently we're using this in our production).
What I need is to link job with the customer. I know it can be done by ticket relations but it's not exactly what I need.
If there will be some possibility of filtering, it can be really nice (like show only tickets from this project / this tracker).
I can write more detailed documentation for this.
We can even pay for development of this functionality.
Thanx :)
More ideas:
- How to make a list of possible tickets filterable: Just create the custom query. In the configuration of the custom field, a user can select custom query (Select or just enter custom query's id) which will filter out possible values.
- Which UI element to use: I have two ideas: Select, for shorter lists and Whisperer for longer lists.
Inter-linking of issues will really move Redmine a lot for other non-sw development projects, like asset/job tracking, etc.
journals
--------------------------------------------------------------------------------
To make sure I understand correctly, you would like a custom field that holds an issue id, right?
And that it could be chosen among the issues returned by an issue query?
--------------------------------------------------------------------------------
Exactly! Basiclly it's for interlinking tickets (Job > Customer). Filtering is just idea, how to implement it. And Custom issue query seems to me as most simple and also most flexible way how to implement it. For example, I have one project+tracker where we have all Jobs and another project+tracker, where we have all our customers (yes, Redmine is really great not only as issue tracker, but as a general business tool!). SO first I was thinking how to "tell" this datatype which issues it should list (display) and then custom query seems to e most flexible way, how to do it. Why?
* It's already part of Redmine
* It's extremely flexible
* It will expanded in the future
* Everyone can adopt their very different scenarios, like list issues from specific project/tracker, user, etc.etc.
--------------------------------------------------------------------------------