But you could have refused the customer in the first place. Nobody forced you to make a contract with him. Of course, once you did, you are compelled to keep up your end of the bargain, and that probably included you doing those jira tasks (you could have probably refused to do entirely different work, like walking the dog of the manager, when you were originally contracted for doing IT development work).
A true contractor in the rideshare space would have an individual contract with each rider, and could of course reject riders based on the terms of the contract (of which the target location is one). However, once a customer is accepted based on the agreed-upon terms (fare, target, number of passengers etc.) he wouldn't be able to throw the passenger out in the middle of the ride for no good reason.
If you now want to say that a rideshare contractor should not be able to reject a customer based upon the terms of the ride, I ask you: why shouldn't he? With whom does he have a contract that binds him? And you say: with Uber. And I say: yeah, and that's why your analogy is fundamentally flawed, why he isn't an individual contractor for each customer but simply an employee of Uber, with whom he has a contract that mandates him to accept all customers that Uber deems acceptable. Exactly like a plumber working at a plumbing company who also has to do plumbing work at any customer his boss sends him to, while his individually contracting plumber colleague can decide to decline or accept customers at his own discretion.