Our supplier has set up a JIRA instance loaded with our requirements.
We tend to respond to any points of clarity raised by the supplier in their JIRA. We also add our own commentary through Comments attribute.
There are occasions when we wish to capture additional information as we’re working through the requirements, eg acceptance criteria. However, we don’t want the client to see such information at least until it has been peer reviewed on our side. Otherwise, there is risk the client may act on incorrect information. We’re currently using a spreadsheet to manage this.
I wasn’t sure how best we approach this in JIRA. Do we set up our own instance of JIRA with one way synch from the supplier’s JIRA so that we don’t send anything we enter in our own JIRA to the supplier? Or do we use protected attributes in the supplier’s JIRA but keep everything in one place? Are there any other options?
Looking forward to responses!
Thanks!
Hi @Vinod Shah
Welcome to the community!
I think you would have limited access to make any changes on the supplier side. There is no straight forward way to achieve what you are looking for. My recommendation is to use your instance that way you do not accidentally update your Client's Jira with the half-baked information.
Hope this helps.
Hi Varsha
Thanks, yes that seems to be the best way forward to ensure the supplier is not exposed to unreliable information.
Many thanks!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.