Hi,
In Jira, we have organised our issues based on provided project types. And often, if there is a busness issue (issue in a business project), we create software issues and link them to the business issue. The software issues are linked between other business and software issues (including subtasks). Then service desk issues are linked to business and software issues. And so on... It can be a mess. But that does not present a problem until we have to give monthly reports for the following:
- Cumulative hours spent on each sefvice desk issue. That would include all issues that were created (not just related) because of that issue.
- Cumulative of hours spent on each business project. Similarly, we need to fetch software issues and subtasks that are related to all the business issues.
- Report on hours spent on all other issues of software projects.
We have looked into several solutions, and all seem to depend on the way the link was created (inward or outward) and the link type that was used. So, my questions are:
1. Is there a way to limit the number of links of a certain link type on an issue? Now you can create two links of the same link type of opposite direction between two issues. Some algorithms don't work if there is a circural reference in the graph of linked issues. We used them directly on database records.
2. Can there be a restricion on who can create a certain link type? Example, only Service desk agents can create a link of type 'causes'. We needed that in trying out the solution with ScriptRunner.
3. Is linking the only way to get this sort of information? Has someone had any expirence with this?
Any suggestion will be helpful!
Thnak you and kind regards,
Marina Veselić
