Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
Next:
badges earned

Your Points Tracker
Challenges
Leaderboard
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Recognition
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Kudos
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Best practices for collaborating with vendors on projects

My client plans to use Jira for HW test case management & HW bug management. The client works with large number of external vendors on testing.

My client's scenario: They have let's say 100 HW test cases defined for a project. They...

  • Need to assign 5 to one Vendor A, 10 to Vendor B, and so on.
  • Want the vendor to see selected information about the test case and also keep all the information about the test cases in a single record. For example, they have internal information which they do not want the vendors to see.
  • Need the vendor to update test case results and upload test result files.
  • Want vendors to be able to report bugs and link the bugs to the test cases.
  • Need to define the test cases ideally in a single project, see the results of all the test cases and create dashboards ideally from a single project.

What is the recommendation for setting up projects and permissions for this scenario?

  • Can Jira classic projects be configured to limit access to specific issues/vendor? This would allow my client to house their test cases in a single project making it easier to manage them.
  • Can Jira classic projects be configured to limit access to specific fields/vendor?
  • What is better - project/vendor OR single project with issues/vendor?

Thanks all for any insights you can provide.

Kalindi

 

1 answer

1 accepted

There are no field security restrictions (I’m sure there is an app that will solve it) so if you can see an issue you can see everything. 

However... there is Issue Security schemes. That would you to have the choice of opening up issues to internal only, internal+vendorA, vendorA only, internal+vendorB etc. 

For more about issue security schemes - see https://confluence.atlassian.com/adminjiracloud/configuring-issue-level-security-776636711.html

Suggest an answer

Log in or Sign up to answer
TAGS
Community showcase
Published in Jira Service Management

JSM June Challenge #2: Share how your business teams became ITSM rockstars

For JSM June Challenge #2, share how your non-technical teams like HR, legal, marketing, finance, and beyond started using Jira Service Management! Tell us: Did they ask to start using it or...

240 views 7 7
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you