---
name: Feature
about: New feature or request
title: ''
labels: feature
assignees: ''

---

## **Describe The Feature**

### **What is the feature about?**

[ A clear and concise description of what you want to be added ]

### **What is the problem?**

[ What is the problem so that we need to add this feature? ]

### **Why is it important?**

[ Tell us why this feature is important or if there is a reason we need to add it soon?]

---

## **Requirements**

### **What it should/shouldn't do**

[ List all the things this feature should and shouldn't do. ]
- This should add '...'
- The '...' should do '...'
- This shouldn't do '...'

### **How it looks like**

[ Describe how it looks like (including name, field type, etc if possible) or add a mock design of the feature if there's any. ]

---

## **Other Notes**

[ Other note such as the feature requirements (ex: the issue is integration with a third-party-plugin), if the customer finds a workaround, note for the developer, alternative solutions, etc. ]
- This is integration with '...' version '...'
- Currently the customer use '...'

---

## **Related Issues**

[ Issues that related to this issue. You can add tags (optional) such as "blocks", "is blocked by", "duplicates", "is duplicated by", "causes", and "is caused by"]
- [is blocked by] https://github.com/NimblyMail/nimblymail/issues/123
- [duplicates] https://github.com/NimblyMail/nimblymail/issues/124
- https://github.com/NimblyMail/nimblymail/issues/125

---

## **Tests**

### Core Acceptance Test

[ The Core Acceptance Test for this issue. ]

Allow changing Lorem into Ipsum
  - Should change Lorem automatically
  - Should ...

### Critical Flows

[ Any item from the Core Acceptance Test (above or in project brief) that should be tagged as critical flows/smoke test ]
- Allow changing Lorem into Ipsum
- Other Core Acceptance Test title

### Automation

[ Existing automation tags or any info to run automation related to this issue ]
  - @feature:feature-name
  - run: `npx playwright test tests/e2e/`
