petn
March 17, 2026, 8:27am
1
Hello,
I would like to create a Pull Request, as I did already before, but for the past days it seems they are restricted to open? Is there a way to become “trusted” or how to create new ones?
There is a bug regarding wrong usage of scrub vs toLowerCase and I fixed this. More Information in this Issue:
opened 08:09AM - 26 Feb 26 UTC
bug
After editing a Sidebar Item in a Workspace (e.g. adding a custom link to a Doct… ype List like "Doc_label_issuance List"), the changes appear correctly immediately after saving. However, after refreshing the page (F5 or hard refresh Ctrl+Shift+R), the sidebar resets: custom items disappear, the workspace switches back to a default/public one, or the sidebar content changes unexpectedly.
This makes the Desk unusable for users who frequently refresh to see updated list data, as their customized navigation is lost.
```json
{
"frappe": "17.x.x-develop (de5fa10)",
"product_management": "0.0.1",
"frappe_desk_theme": "1.0.0"
}
```
Perhaps there is some setting or configuration option somewhere that can make the customized sidebar persist across refreshes?
This small fix may also fix these issues:
opened 06:37AM - 01 Feb 26 UTC
bug
## Description of the issue
I have tested this on a custom app, my custom app ha… s three workspace sidebards. When I enter one and click on a link (doctype) I can work adding data to the form (no problem). But the moment I do a refresh (and hard refresh as well ctrl + shift + r) it forgets which sidebar its on and reverts to the first sidebar created for that app. this disorients the user. because sometimes they refresh to see new data in a list but now their sidebar has changed to something completely different.
This does not happen with standard erp modules. only with custom apps, not sure why.
## Context information (for bug reports)
**Output of `bench version`**
```
erpnext 16.3.0 version-16 (83a0d95)
frappe 16.4.1 fix-page-workspace-sidebar (ae3e0f5)
garments_manufacturing 0.0.1 develop (7c0ce90)
hrms 16.2.0 version-16 (0038cfc)
```
## Steps to reproduce the issue
1. Click on a workspace, then click an app.
2. Refresh
3. You will see sidebar has changed.
### Observed result
Workspace Sidebar changes
### Expected result
Workspace Sidebar should not change on refresh.
## Additional information
OS version / distribution, `Frappe` install method, etc.
opened 01:37PM - 25 Jan 26 UTC
feature-request
I'm frustrated with the new sidebar behavior in Frappe v16. When I open a linked… DocType from another module, the entire sidebar context automatically switches to that module's workspace. This is disorienting - I lose track of where I started and there's no intuitive way to return to my original workspace context.
For example, if I'm working in the Accounting workspace and click on a linked Customer, the sidebar suddenly switches to the CRM workspace. I then have to manually navigate back to where I was.
**Describe the solution you'd like**
The sidebar should remain fixed and consistent when navigating between modules. The workspace switch should only happen when I explicitly navigate to a different workspace via Desktop or the workspace switcher.
This way, if I'm working in the Accounting workspace and click on a linked Customer, I stay in my current sidebar context while viewing the Customer document. My navigation reference point is preserved.
**Describe alternatives you've considered**
Add a setting option in User Settings or System Settings:
"Keep sidebar fixed - switch workspace only on explicit user action"
When enabled, I would maintain my current sidebar context regardless of which DocTypes I open. This would give users the choice between the current automatic switching behavior and a fixed sidebar approach.
**Additional context**
This would give users control over their navigation experience and preserve mental context during complex workflows that span multiple modules. The current automatic switching breaks the workflow for users who prefer a fixed reference point while navigating related documents.
opened 01:55PM - 09 Feb 26 UTC
bug
### Information about bug
I was on my desk and added the Home icon.
After click… ing on the icon, I landed in /Stock/Item with the Home Sidebar
<img width="643" height="314" alt="Image" src="https://github.com/user-attachments/assets/124d3cbf-0e38-4530-8889-ebc0b31e0b32" />
After reloading the page, the sidebar changes into the correct one for Items, the Stock sidebar.
<img width="533" height="467" alt="Image" src="https://github.com/user-attachments/assets/d2b26987-b46c-4bfd-8324-94c2042540a7" />
When navigating back to the desk page, the icon is no longer selected.
Besides this, I have also encounted several other bugs in this direction, within minutes of testing. Please tell me if more information is needed on specifics.
### Module
stock
### Version
frappe: 16.5.0
erpnext: 16.4.1
hrms: 16.3.1
### Installation method
docker
### Relevant log output / Stack trace / Full Error Message.
```shell
```
opened 08:39AM - 12 Mar 26 UTC
bug
If a DocType belongs to a module and is added to a custom workspace sidebar, ref… reshing the page changes the sidebar to the auto-generated module sidebar.
**Steps to Reproduce**
1. Create a module **TestA**.
2. Create a DocType under module **TestA**.
3. Create a workspace **Test**.
4. Add the DocType to the **Test** workspace sidebar.
5. Open the DocType from the workspace.
6. Refresh the browser tab.
**Behavior**
Sidebar switches to the auto-generated **TestA** module sidebar.
**Note**
If the workspace name and module name are the same, the issue does not occur.
**Version**
frappe: 16.11.0
Pull request is restricted now, However you can still contribute by sharing your branch details (w/ the fix) in the corresponding issue.
2 Likes
petn
March 18, 2026, 4:32pm
3
Thank you for helping me out. Fixed the commit but now there are 2 failed automatic tests, which should not even belong to this commit. However thank you very much because this small fix may help a lot in UX.
ankush
March 19, 2026, 6:38am
4
FYI: Suspension of community PRs · Issue #38145 · frappe/frappe · GitHub
(Pull requests are restricted, but you can consider sending patch file or branch. Maintainers can then “pull” it into core.)
2 Likes