[bumelant]

If the requirement is coming from accounting (qualification of spend as capex) there’s no way to push back, but it also doesn’t mean you need to follow the exact process of bigger company. You can negotiate minimum amount of documentation that for legal reasons your team needs to track in JIRA and do just that. Good luck!

[burfog]

Wouldn't that goal (qualification of spend as capex) be solved better by timecards? I don't see how a bug tracker helps unless you abuse it to be a timecard system.

Of course, timecard software can be awful too.

[cimmanom]

Jira has a field for time spent on a ticket, and can produce reports about it pretty quickly. There are also plugins available to let developers use various timers with it, or even integrate with timesheet tools like Harvest.

I’ve worked in a company that qualifies development time as capex. They can’t just treat all developer butt-in-seat hours as capex. They have to allocate it to specific projects.

Using the issue tracker for that can streamline the process and saves the developer having to know which bucket to bill time against for each ticket, because the project manager or whoever can take responsibility for tagging each ticket with the appropriate accounting bucket.

And time spent on maintenance or meetings or peripheral tasks like interviewing candidates or configuring Jira goes into its own buckets that can’t be capitalized. Using the issue tracker to track capitalizable time makes that delineation easy to enforce. If it’s not in the issue tracker, it’s not capitalizable.

[bumelant]

That would be one of the options - I have used Primavera in one of my previous jobs. But I assume from the question that the company has decided to use JIRA for that purposes.