Jira Assets & Automation Setup
Budget: €30 – €250 EUR
I want my Jira Service Management site to act as a single, trustworthy source for every piece of hardware-software information we hold—particularly the contracts that sit behind those items. To get there, I need an Atlassian-savvy expert who can:
• Build or refine an Assets (Insight) schema that captures Software Licenses & Installations as well as our Domain Names, Security Certifications, and Supplier Contracts.
• Import the existing data (CSVs/PDFs) and configure object types, attributes, custom fields, and issue links so technicians can see at a glance which contract or licence is tied to any ticket.
For contract management I also need two Automation for Jira rules:
• Automatic reminders X days before a contract or licence is due to expire, sent to both the asset owner and our procurement inbox.
• Real-time notifications whenever a key detail changes—renewal price, supplier, scope, or SLAs—so stakeholders are always up to date.
Please make sure the rules work in both company-managed and team-managed projects, use smart values for dynamic dates, and are fully documented inside the rule description. A short walkthrough video or screenshots that show the schema, sample issues, and fired automation logs will be the acceptance test.
• Build or refine an Assets (Insight) schema that captures Software Licenses & Installations as well as our Domain Names, Security Certifications, and Supplier Contracts.
• Import the existing data (CSVs/PDFs) and configure object types, attributes, custom fields, and issue links so technicians can see at a glance which contract or licence is tied to any ticket.
For contract management I also need two Automation for Jira rules:
• Automatic reminders X days before a contract or licence is due to expire, sent to both the asset owner and our procurement inbox.
• Real-time notifications whenever a key detail changes—renewal price, supplier, scope, or SLAs—so stakeholders are always up to date.
Please make sure the rules work in both company-managed and team-managed projects, use smart values for dynamic dates, and are fully documented inside the rule description. A short walkthrough video or screenshots that show the schema, sample issues, and fired automation logs will be the acceptance test.