How to associate certain fields to only certain STATUS?

[Jan Šimek]

Hi I would love to know how to associate certain fields to certain statuses. Lets give an example:

If I will want to show certain field only in status Contract, but not in the others and then show it only at the end, when the task is complete - like a summarization, is there any way how to do it? 

I found, that you can connect fields to some phases like CREATE; EDIT/VIEW, but not sure how to do it with certain status.

Also is there any way how to create a subtask in some certain status and then hide it and show different subtasks? Of course if we would know their names etc.

Thank you

[Nic Brough -Adaptavist- · Accepted solution]

There's no way to do this, fields are data on issues, and hence they're always there.

What you can do is not offer the field for create/edit in general, and only ask people to fill it in during a relevant transition.  My usual example of that is when you have an Incident issue type - you probably want fields for "root cause analysis", but, you don't expect them to be filled until the users push the incident from "fixed" through to "analysed"

Create, edit and view are not "phases", they are actions - things you can do to an issue.  What you're looking for is "status" - the indicator of where an issue is in its lifecycle.

On the sub-tasks - no, again, a sub-task is part of an issue, it would be nonsense to hide it from the issue at all, let alone hiding by status or other data on the issues.

[Jan Šimek]

Hi Nick, 

I get your point, but the thing is when you are creating reporting system it needs to be quite a resistant, otherwise people will find a way how to play with it. And asking somebody to not fill exact field, but fill different one is not for sure one of them. That is why I am asking for solution.

Thanks

[Nic Brough -Adaptavist-]

Yes, so only offer the fields for entry when people are moving the issue into a new status.  That's how you should be trying to control data entry.