Are you in the loop? Keep up with the latest by making sure you're subscribed to Community Announcements. Just click Watch and select Articles.

×
Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Linkage to multiple issues

Greetings !

We have a product developed and currently serving the client with a situation one client and one provider limitation

Now, our client has multiple providers. So we need to revise the design for the current product

There are different Jira projects created for different purposes

1. Project management Project - Project (Issue Type) // All providers can view this data

2. Release Management Project - Release (Issue Type) // All providers can view this data

3. Contract Management Project - Contract (Issue Type) --> Context is separated for multiple providers with a permission scheme set that resources from one provider should not be allowed to see the data of another provider in this Jira project

Each of these have others issue types

For example Project Management has a Issue type "Weekly Status Report"

which needs to separated as below

Project 1

     - Contract 1 (Provider 1)     --> Release 1    ---> Status Report for week 1 (Provider 1)

     - Contract 2 (Provider 2)     --> Release 1    ---> Status Report for week 1 (Provider 2)

 

     - Contract 3 (Provider 1)     --> Release 2    ---> Status Report for week 30 (Provider 1)

 

Project 2

- Contract 4 (Provider 1)     --> Release 1    ---> Status Report for week 1 (Provider 1)

 

So a single project can have multiple contract and each contract could be spread across single/more releases.

Project

    - Linked to multi contracts ( via multi-field selection)

 

Requirement : A weekly status report must needs to be identified uniquely for the Project + Contract + Release.

 

Is linking "Status Report" issue to issues Project, Contract and Release allowed as multi-primary keys ?

 

 

0 answers

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
SERVER
TAGS
AUG Leaders

Atlassian Community Events