JIRA is an issue tracker, not designed for random arbitrary items. It groups issues into projects, and then boards look at ranges of issues.
Could you explain what you're actually looking to do here? What is the benefit of this X for the end user?
@Nic Brough [Adaptavist], we just don't want to use JIRA as a Bug Tracking Tool. It's a Task management tool cum product management as well.
What I want to do: [considering Team as Board and Product as Project in JIRA]
Help me here. Or suggest an alternate.
Yes, it is, but you don't need arbitrary objects to do any of that. Just issues.
Epics need to live in projects as they are issues, but that doesn't stop issues from other projects being added to them.
For another layer of items like that, try Portfolio
In the past, Portfolio for Jira required a high degree of detail–foresight that was unrealistic for many businesses to have–in order to produce a reliable long-term roadmap. We're tur...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs