Hi there,
We are thinking of using Insight for our Contract management.
I don't find any documentation on this kind of use case for Insight.
The big picture is
1- Negociation, planification and follow up are made on with Jira Issue
2- Jira Issue is linked to a Contract Object in Insight
3- Contract Object may linked to licences or contractors Object in Insight
4- We have reminder and Jira Issue open automatically on due dates
I have then no doubt that we will be able to use Jira and insight reporting tools.
What do you think ?
Do you have any idea, recommendation or experience to share ?
Hi @Patrice Champet,
You sure can use Insight for contract management as you described. I would add the following attributes to a Contract object:
Hope this helps,
- Manon
Thanks @Manon Soubies-Camy, it confirms our first idea.
Do you know if Insight is still available for Jira Software DC ?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Patrice Champet ,could you please share how you accomplished this task in Jira Service Management or Jira? I ask because I recently designed the contract information under asset in JSM, but encountered several limitations. This made me wonder if designing contract management under JSM is the best approach. I would be grateful for your advice.
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Moon
I guess that there is a clear design to be done and a classification of the data you need for managing contracts.
To my current understanding Assets is more to be used to store some metadata regarding the contract and lifecycle of the contract it self.
Especially if you are going to have several activities that may be linked to the contract object it self.
Then other contract information, as far as you don't need them to manage contract lifecycle or dependency (with providers for instance) should be on the contract it self the may remain a file or a confluence page link to the asset.
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.