Separate create issue type screen content

[Dominik M.]

Greetings,

 I am the administrator of two projects created with shared configuration (Project-C was created after the Project-B and its based on the latter one mentioned configuration) - what I need to do is to have  "Description" field removed from the issue type "task" on "create issue" screen - only in Project-C, Project-B config. should not be included under those actions. Moreover other issue types in Project-C also should not be affected and have "Description" field present.

In case of custom fields you can use context to get fields displayed with different options (e.g. dropdown menu fields), however "description" field is not a custom one and every time I try to do this I get all issue types with or without description field, whilst there's no way to get only Project's-C "task" issue type affected.

Advice of any type is highly needed and appreciated.

Regards,

Dominik Maciejewski

[Thomas Schlegel]

Hi Dominik,

you have to create a seperate Field Configuration and a seperate Field Configuration Scheme for Project C.

• First, make a copy of your existing Field Configuration of Project C
• Edit the copy, rename it to project-c-task or so
• Then configure the new field configuration:
  • Hide the field "Description"
• Make a copy of your existing Field Configuration Scheme of Project C, so that it can be seperated from Project B
• Edit the Copy, call it "Project C Field Configuration Scheme" or so
•  Then configure that new Field Configuration Scheme
  • Associate the issue type "Task" with the Field Configuration "Project C-Task" and save it

Now, the field "description" should be invisible for tasks.

[Dominik M.]

Superb tutorial - works like a charm. I'm really thankful Thomas. One more time many thanks.

P.S. For anyone reading this - please remember to assign "Project C Field Configuration Scheme" to Project's C (GP-->cog icon-->fields-->actions-->use different scheme and select from the dropdown the dedicated one - in my case it's "Project C Field Configuration Scheme")

All the best,

Dominik

[Thomas Schlegel]

you're welcome :-)

[Dominik M.]

to make it fully done:

accessed project C, used GP shortcut

I've associated:
--> create issue screen with PROB: Scrum Default Issue Screen (Description Field must be ABSENT HERE)
--> edit issue with Copy of PROB: Scrum Default Issue Screen (Description Field must be PRESENT HERE)
-->View Issue with Copy of PROB: Scrum Default Issue Screen (Description Field must be PRESENT HERE)

by doing so I have "Description" field removed from the "create issue" screen and present when editing and viewing the issue.

Unfortunately it affects all issue types (and I need it only on task issue type). I've noticed that "Bug" issue type isn't affected by this and it works as the "Task" issue type as it uses its own "Bug Only Issue Type Scheme":

I'll investigate the issue and consult it with my manager.

[Joe Pitt]

Field configuration schemes can be made up of field configurations for each issue type. It sounds like you need one for task issues and one for all others. 

[Dominik M.]

Correct, here's the final part which in fact led to Description's field in Task Issue type in Project C to be present only on create issue screen (vs Project-B where it should've been left with Description Field on Create Issue screen)

so far, so good except the fact that issue type screen schemes are shared for 2 projects.

what needs to be done here is now FIRST to differentiate project's B screen schemes from project C and then amend them.
I've copied PROB: Scrum Issue Type Screen Scheme and saved it as PROC: Scrum Issue Type Screen Scheme, then it was associated with Project-C

now it's time to do amendments only for Project-B Task Issue Type:

outcome:

and testing phase time!:

above everywthing nice and smooth as it should be

Project-B:

edit screen/view screen tests were done as well and description field is present for task issue type in Project's-C only on create issue screen.

all works fine - many thanks to all contributors - I hope my manual will save much time for other admins.