what kind of fields to use ?

what fields do you guys use to get information from customer request or change requests? i'm trying to figure out what type of information i need. I have put a field with a list of projects they can pick, completion date, company name etc.

2 answers

This is very vague question. Isn't this something which completely depends on your project usecase and customers? In general text fields are a bad idea if there are reporting requirements based on that field



i'm trying to see what everyone uses as we are creating a project and we are gathering ideas. I wanted to see what everyone has used and see if that helps.

I'm afraid Renjith is right - Jira is immensely flexible and the answer really is "what do YOU want to do?" I approach this with my stock set of "how do I use Jira" tips. First, talk to your users. Second, think of the question "What do you want to report on"? Your reports and what your users want to get OUT should drive your choice of fields. But we can't tell you what your users want or need - we need to talk to them to find out!

Yes, Jira is flexible, but not everything is fine. And why not learn from each other. I think, this is also the intention of "answers".

The whole point Renjith is making, and I'm supporting, is that there is not a lot to learn. How I do CRs for one client is wildly different from how I do it for another. And both of those methods are probably bad, if not utterly useless, for you and John. There's little value in sharing them because they are unlikely to be useful. The best answer for this really really is "work out what works for your teams and do that". I'm currently sitting in an Atlassian talk about something very similar, and they're telling us how some of the latest features for the Atlassian products have been built with exactly that in mind. Look at your own usage, don't try to do what other people do because it probably isn't the best way to do it yourself.

Again, to reiterate Renjith and Nic, you're actually dealing with at least two separate processes so the fields needed may be entirely different. Coming from an ITIL background, to me a customer request implies a need for information while a change requests deals with mitigating risks to production while changing configurations. I'd recommend, reviewing the processes being used and, as stated, meet with your stakeholders to determine what fields are needed for the issue types in question.

well the main point was to gather ideas. Does not matter how the processes are done or anything like that. The stakeholders do not what they want at the moment and i just figure out i could get information or ideas from the community that is the whole point of having this place. If it works or not that is for us to decide and that is why i wanted to see what different ppl did.

But that's the difficulty as well. I mean - does your business process involve penguins? If it does, then I'd suggest thinking about a select list for their species (17 options if memory serves), and a text field for describing each individual. If it's cars, have a look at components, a swathe of select lists and probably several text fields. I can still absolutely guarantee you that other people's data is of little use to you. Your whole question really really is "think for yourself, analyse what your processes are, ask your users what they need, think about reporting, etc".

If you know, what kind of Information you need to have in Jira, you can evaluate which fields and field types you should use for that. There is a lot to consider, as already answered. In some cases, regarding Text Fields, I found it very useful to use the "Wiki Style Renderer". This can be defined in the Field Configuration.

In addition: The Wiki Style Renderer is useful for hyperlinks, lists and a lot more. But if you need plain text, you shouldn't use it.

thank you this is the type of information i was looking for.

Suggest an answer

Log in or Sign up to answer
Community showcase
Published Nov 27, 2018 in Portfolio for Jira

Introducing a new planning experience in Portfolio for Jira (Server/DC)

In the past, Portfolio for Jira required a high degree of detail–foresight that was unrealistic for many businesses to   have–in   order to produce a reliable long-term roadmap. We're tur...

2,595 views 17 21
Read article

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you