Content
View differences
Updated by Dominic Bräunlein over 1 year ago
### Steps to reproduce
1. Login as an admin user
2. Make sure to have enterprise enabled
3. Go to administration -> work packages -> types -> any type -> subject configuration tab
4. Click on "Automatically generated subjects"
5. Type in any character to open the suggestions
### What is the buggy behavior?
* The field is taking up the full width of the browser, but [according to the designs](https://www.figma.com/design/I2IVNb97j1fNNCs32H6p2m/Automatic-generated-subjects?node-id=0-1&p=f&t=2DtpPPNwFjOGgF5Z-0) it should take only half
<img class="op-uc-image op-uc-image_inline" src="/api/v3/attachments/308460/content">
* Separators are overflowing past the suggestions box
<img class="op-uc-image op-uc-image_inline" src="/api/v3/attachments/308459/content">
### What is the expected behavior?
_Describe how the application should behave like. Example:_
1. Width of the field according to design
2. Dividers not overflowing
<br>
**Technical notes**
* Two possible solutions
* Input width possibility is added to the input and can be defined like for other form fields
* Do not add possibility of width changes and solve the problem by moving forms into containers. This would also solve the CKEditor width problem.
* Additional input from Primer Design team is needed
1. Login as an admin user
2. Make sure to have enterprise enabled
3. Go to administration -> work packages -> types -> any type -> subject configuration tab
4. Click on "Automatically generated subjects"
5. Type in any character to open the suggestions
### What is the buggy behavior?
* The field is taking up the full width of the browser, but [according to the designs](https://www.figma.com/design/I2IVNb97j1fNNCs32H6p2m/Automatic-generated-subjects?node-id=0-1&p=f&t=2DtpPPNwFjOGgF5Z-0) it should take only half
<img class="op-uc-image op-uc-image_inline" src="/api/v3/attachments/308460/content">
* Separators are overflowing past the suggestions box
<img class="op-uc-image op-uc-image_inline" src="/api/v3/attachments/308459/content">
### What is the expected behavior?
_Describe how the application should behave like. Example:_
1. Width of the field according to design
2. Dividers not overflowing
<br>
**Technical notes**
* Two possible solutions
* Input width possibility is added to the input and can be defined like for other form fields
* Do not add possibility of width changes and solve the problem by moving forms into containers. This would also solve the CKEditor width problem.
* Additional input from Primer Design team is needed