Redmine

This relates to #638, issue relations between projects:

I have one redmine project for people outside the company to submit issues and features.
Then, I have another project that is for internal use by engineer(s).

The two levels allow me to have a development plan that determines which public issues become internal issues, and lets me assign and prioritize them appropriately. The mapping is not one-to-one. For some small tasks, the internal and external issues may be the same. However, Larger external requests might be broken into smaller internal tasks. Some external requests might be ignored. Some internal tasks (like server maintenance) might be added without an external request.

The public should never be able to assign work directly to engineers, and only certain engineers should be able to reply publicly to customers.

The ugly solution is copy & paste issues between projects. But this maintains no linkage, and requires duplication of data. Relations are a better way, but they need an additional feature:

Relations would need an option to be 'one-way' or unidirectional. E.G. A task on Project A refers to a task on project B, but B does not make any mention of the link to A. So an internal worker can see a reference to the external request, but people outside the company do not see the links to internal issues.

Just hiding the reciprocal link, when requested, might be enough to implement this feature.

Going one step further, a person with the correct Role & permissions (such as a manger), could see the link from both the internal and external project (it might appear different to indicate it is otherwise invisible). This way, it becomes easy for them to check if a related task has been resolved.