Looking for Best practices to keep customer contract and finance information thru Jira?

[Sandra Lawrence]

We are working with multiple vendors and need to keep not only their project development but, keep key vendor information (contract, clin, financial, project(s), stop/start dates, etc).  I am wondering what others have established as a best practice to maintain vendor information?  (FYI - already use Jira for development projects).

[Harald Seyr]

Hi @Sandra Lawrence 

maybe you check if use of Jira and Confluence can help in this case. In the company I work (and those where I worked in the past), we always used Confluence to keep up to date info in a "wiki".

• Jira is for tasks, they start and end, after end they are no longer important (except maybe for a knowledge base)
• Confluence is for information / documentation that evolves over time, has a current state and a change history

We had a page (or a page tree with subpages) for a vendor or customer where important information is available, open projekts / tasks / issues are in Jira. The good integration of Jira and Confluence allows easy links between issues and pages.

Regards,

Harald

[Riley Venable]

You can use labels on each issue to track the location of large items tracked as assets. You can also use components to track by the department to see where the main volume of requests is coming from. Additionally, you can create an issue for each purchase request or for each item/service being purchased (if they are large). You can also set due dates to review service agreements and claim upgrades. Finally, you can treat each item on your board as a document. This way, you'll always know the status of each piece of work.

[Trudy Claspill]

This appears to be similar to this other post:

https://community.atlassian.com/t5/Jira-questions/what-is-the-best-Jira-template-if-you-want-to-keep-track-of-all/qaq-p/2270403