Allow user to define custom shared page layout
Description
On global/project settings we should be capable to define default layout,
on share level user can override or revert to default settings.
Child issues
ESFJ-176
Custom shared Issue layout
Released
ESFJ-177
Add Ability to Reorder Columns in Filter Share
Withdrawn
ESFJ-178
Introduce board card customization options
Released
ESFJ-214
Filter (JQL) share table customization
Released
ESFJ-559
Board card color customization
Released
ESFJ-666
Refactor board card layout customization ui and display board card on external board
Released
ESFJ-735
The following has evaluated to null or missing: ==> lightMode[priorityName]
Released
ESFJ-745
Labels / title as in jira - on mouse hover
Released
ESFJ-746
On hover - annonymous user should be visible
Released
ESFJ-747
Fix perfomance issues on color board form (remove redundand calls and make rest pararell)
Released
ESFJ-748
Card layout tab rename to Card config
Released
ESFJ-749
On board card config list show few first items
Released
ESFJ-750
Add to field type number or string check if it's a hash(nullpointer)
Released
ESFJ-754
Fix priority nullpointer board-index.ftl4
Released
ESFJ-765
Board card field freemarker.core.NonHashException
Released
ESFJ-767
Fix non working card color customization
Released
ESFJ-797
Test similar issue before migration
Backlog
ESFJ-798
Make field "Rest of custom fields" sort alphabetically
Backlog
Linked issues
duplicates
ESFJ-127
Shared page customizations
ESFJ-127
Shared page customizations
Withdrawn
Activity
Show:
Details
Priority
MediumAssignee
Igor Hercer
Reporter
Krzysztof Bogdan
Fix versions
Roadmap
Created
8 June 2022, 13:31
Updated
13 March 2024, 16:45
More fields
Created: 8 June 2022, 13:31
Updated:
13 March 2024, 16:45
@Krzysztof Bogdan Every task is done, moving status to done.
Hello @Krzysztof Bogdan
This is the best moment to add more description, wire-frames, comments.
Why we doing this?
What is expected result?