•  
     
    story #12188 hide fieldsets according to state
Summary
tracker admin
hide fieldsets according to state

I can simplify usage of artifacts by displaying only the relevant amount of informations at a given workflow state

Overview

This show/hide feature is a "soft" hiding of the fieldsets meant to present something simple. Advanced user would still have access to all the fieldsets with a "Show all" or progressive expand/collapse is they want to.

This story depends on story #12187 for new workflow configuration panel.

Functional overview

Tracker administrator point of view, configuration

By default, all fieldsets are displayed (current state) and there is a new section in the workflow transition configuration to select the fieldsets that are hidden.

It only applies on Fieldsets "containers" (it's not possible to hide a given field or a column for instance).

It's configured as a "Post Action", it means that the fieldset will be hidden after an artifact reach a given state.

In order to keep a clear UI and not make it confusing, this post-action can only be added once per state. After adding it once, when you try to add this type of post-action again, then the selectbox for post-action type will show a disabled option.

End user point of view, usage

On page load (either artifact view or Angular Modal) fieldsets that are hidden by configuration are not displayed.

There is a button in the interface "Show all fields" (or equivalent, like in "Chrome" configuration "Advanced mode") that shows all the fieldsets. The load shall not loose user work if she already started to work/modify the artifact.

It's not possible to switch back to "hide fields" once "Show all fields" has been clicked but next load of the artifact will hide fieldsets by default.

Edge cases:

  • Mandatory fields: a field might be mandatory, hidden and empty. In that case, the containing fieldset will be displayed regardless of the configuration made by tracker admin.
  • Field dependencies: when 2 fields are connected with a field dependency, both fields must be in a fieldset with the same status: either both are displayed or both as hidden. When at least one is displayed, the other one's fieldset is automatically displayed as well regardless of the configuration made by tracker admin.
  • Email notifications: emails are not impacted by this change and are sent with all values.

Technical overview

  • Hidden fieldsets are added in REST routes (esp. /artifacts/:id for modal)
  • Configuration must be exported/imported with tracker XML format
  • Configuration must be duplicated at tracker / project creation.

 

 

Empty
duffey maxime (duffeym), Jordan BACHELET (jordan_bachelet_jtekt)
Status
Empty
Done
Development
  • [ ] Does it involves User Interface? 
  • [ ] Are there any mockups?
  • [ ] Are permissions checked?
  • [ ] Does it need Javascript development?
  • [ ] Does it need a forge upgrade bucket?
  • [ ] Does it need to execute things in system events?
  • [ ] Does it impact project creation (templates)?
  • [ ] Is it exploratory?
Empty
Details
#12188
Manuel Vacelet (vaceletm)
2019-06-28 11:53
2018-08-27 16:29
4136

References
Referencing story #12188

Git commit

tuleap/tuleap/stable

Refactoring: delete unused code d23cf54912
Refactoring: distinguish display and submit for containers 4870e34840
Refactoring: move existing tests to PHPUnit 23076a9767
Hide selected fieldsets in artifact view 27edcbef09
A fieldset cannot be deleted if used in workflow post action 69725e2b34
Extract "fieldset must be hidden" in a dedicated object f74b4657d5
Fieldset is not hidden if it contains a mandatory field 164f6ccc7b
Deal with TTM trackers 62748fac19
Do not hide a fieldset if a field in it is part of a field dependency 8888620573
Refactoring: form element representations are build in a dedicated object a31b5abfef
Hidden fieldsets are returned by the REST route artifacts/:id 577ac09698
Return hidden fieldsets actions in REST GET /tracker_workflow_transitions/{id}/actions 4c583cadc4
Duplicate hidden fieldsets actions at transition creation 8184fcfe06
On switch from Simple to advanced workflow, delete post-actions 3a70767067
The parsing of Tracker_REST_FormElementRepresentation breaks the generation the OpenAPI specification file 474dba3ddc
Duplicate post action at tracker and project creation 73ac507a4b
Create hidden fieldsets post action via POST tracker_workflow_transitions/:id/actions 4ab7bce538
Add a button to show all hidden fieldsets in artifact view 66d010bf5f
XML import of hidden fieldsets postaction e63fbb5f6f
Post actions in XML must not have a defined order deaaf2a19d
XML export of hidden fieldsets postaction 84cb11631d
Configure Hide Fieldsets in web UI ca8f69c9a4
Have show hide fieldsets option in Ear-Modal c81eb22fd3
Add Show/Hide hidden fieldsets to Angular Modal 7d11579814
Remove Hidden Fieldsets feature flag 5d1b1def3e
Remove duplicated warnings at workflow mode switch 3b1c6f8c5f
Remove simple mode trick in CIBuild Json Parser a9e4b123a4
Remove simple mode trick in SetDateValue JSON Parser e0d0368787
Remove simple mode trick in SetIntValue JSON Parser f416f1cf8c
Remove simple mode trick in SetFloatValue JSON Parser 13ea2e4457
Remove all usages of IDs in postactions update process 8db0ce5c43
Cannot create hidden fieldsets post action in TTM trackers 993ba821d4
Deal with TTM trackers 3b475612d6

Follow-ups

User avatar
Martin GOYOT (goyotm)2019-05-21 15:10
  • Acceptance criteria
    Something went wrong, the follow up content couldn't be loaded
    Only formatting have been changed, you should switch to markup to see the changes
User avatar
Joris MASSON (jmasson)2019-03-05 16:42
The new post-action can only be added once

  • Acceptance criteria
    Something went wrong, the follow up content couldn't be loaded
    Only formatting have been changed, you should switch to markup to see the changes
User avatar

Update after team's review


  • Acceptance criteria
    Something went wrong, the follow up content couldn't be loaded
    Only formatting have been changed, you should switch to markup to see the changes
  • CC list set to Jordan BACHELET (jordan_bachelet_jtekt), duffey maxime (duffeym)
User avatar
  • Acceptance criteria
    Something went wrong, the follow up content couldn't be loaded
    Only formatting have been changed, you should switch to markup to see the changes
User avatar
  • I want to
    -Show/hide fieldsets according to state 
    +hide fieldsets according to state 
  • Acceptance criteria
    Something went wrong, the follow up content couldn't be loaded
    Only formatting have been changed, you should switch to markup to see the changes
User avatar
  • I want to
    -Show/hide fields according to state 
    +Show/hide fieldsets according to state 
  • Acceptance criteria
    Something went wrong, the follow up content couldn't be loaded
    Only formatting have been changed, you should switch to markup to see the changes
User avatar
  • So that
    Something went wrong, the follow up content couldn't be loaded
    Only formatting have been changed, you should switch to markup to see the changes
  • Acceptance criteria
    Something went wrong, the follow up content couldn't be loaded
    Only formatting have been changed, you should switch to markup to see the changes