Does it really take 720h to create and customize JIRA project?

[Tomasz R]

Hi community,

I work for a big multinational that is using JIRA (server version). I need to setup a JIRA project for my team. I don't need anything fancy, my basic requirements are:

1. about 25 custom fields for epics, a few of them with a drop down list, a few with checkboxes and a few of them mandatory. Everything available in single tab on edit/create/view screen.

2. simplified JIRA workflow turned on, or alternatively a 10 step workflow with any to any transition model

3. Import issues from legacy JIRA project on different instance (I will prepare loader myself) 

4. default issue types, no screen customization beyond what described in point 1, no automations, nothing really besides the custom fields that I need for reporting

In my company, I can't set it up by myself, I need to go through technology support team. They estimated that this work will require 720 manhours of effort from them (they came down from 1080h estimate after some pushback). They will first do it on UAT and then after my approval move it to production.

Now, from my experience working in similarly sized corporations, I was typically, placing a ticket, or calling tech support for such requests and they were done in a few days. Also if I needed to add a few new custom fields to existing project, they were doing it for my while we were on a phone, in a matter of minutes.

I would appreciate if you could comment on this estimate - I'm convinced that it is completely out of touch but maybe I'm missing something? How much effort would it take from your experience?

[Nic Brough -Adaptavist-]

Welcome to the Atlassian Community!

No, that is a ridiculous estimate, an experienced Jira admin could probably do most of that in under an hour (the exception might be the import of issues, depending on size and complexity)

[Vamsi Kandala]

Hi @Tomasz R

While I don't say that it will take under an hour, after going through your requirements and having created some of the similar sized projects before, I can easily say that it will not take more than a week for a single person (experienced one if I may add) to do this in the lower instance (UAT) and implement the same in PROD.

So, on an average it should not take more than 40-56 hours (if you take 2 man-hour days for buffer).

Hope this helps.

Thanks,
Vamsi

[Nic Brough -Adaptavist-]

We just had a request similar to this go through our "Assist" service.

I know that is an advert, but I am hoping you might see it as an example rather than an ad.

Bob (name changed for privacy) created 30 custom fields, adding all the needed options to the ones that were select lists, then the project, then the 22-step workflow, with all the conditions, validators, and post-functions and automation.  Then they solved 8 other support calls and got tired and went out for lunch.  A morning, not a month.

Seriously, your requests could be measured in minutes, not days.

You really need to question your admins.

[Harald Seyr]

HI @Tomasz R 

Since you ask for a comment, I will give my 2 cents: This estimate is a typical response from a department in a larger company that wants to avoid to work. 

Basically, it means "go away".

However, please allow me to comment on your requirements also: Adding 25 custom fields and a workflow with 10 stati smells like overengineering.

I suggest to start with the most simple three status workflow (Todo, In Progess, Done) and dont use any custom field until you really need them. 

When you need specific custom fields, you can always request them one at a time and (hopefully) get them for free.

Regards,

Harald