feat: Add Jira issue creation guidelines and templates

*   Added new `.cursor/rules` to guide AI on creating Jira issues.
*   Introduced `jira-formatting.mdc` to define Jira Markdown syntax and
formatting requirements.
*   Included `srvkp-jira-template.mdc` for creating new Jira stories using a
standard template.
*   Provided `srvkp-jira-bug-template.mdc` for generating Jira bug reports with
a specific structure.
*   Ensured AI output for Jira issues adhered to correct Jira Markdown and
company templates.

Signed-off-by: Chmouel Boudjnah <[email protected]>

Author: chmouel

.cursor/rules/jira-formatting.mdc

@@ -0,0 +1,30 @@
+---
+description: Ensures new Jira issues are formatted with correct Jira Markdown
+alwaysApply: false
+---
+
+# Jira Issue Creation and Formatting
+
+When asked to create a Jira issue (story or bug):
+
+1.  **Identify the issue type:** Determine if the user wants a "story" or a "bug".
+2.  **Use the correct template:**
+    *   For stories, use the content from `.cursor/rules/srvkp-jira-template.mdc`.
+    *   For bug reports, use the content from `.cursor/rules/srvkp-jira-bug-template.mdc`.
+3.  **Fill in the template:** Populate the template with the context and details provided by the user.
+4.  **Output in Jira Markdown:** Ensure the entire final output strictly adheres to Jira's markdown syntax. Do not use standard markdown.
+
+## Jira Markdown Quick Reference
+
+*   **Headings:** `h1.`, `h2.`, `h3.`, `h4.`, `h5.`, `h6.`
+*   **Bold:** `*bold text*`
+*   **Italic:** `_italic text_`
+*   **Strikethrough:** `-strikethrough-`
+*   **Monospaced:** `{{monospaced text}}`
+*   **Bulleted List:** `* item` (or `- item`)
+*   **Numbered List:** `# item`
+*   **Blockquote:** `bq. Blockquote`
+*   **Code Block:** `{code:language} ... {code}` or `{noformat} ... {noformat}`
+*   **Link:** `[link text|http://example.com]`
+
+Always produce a clean, copy-paste-ready output for a Jira text box.

.cursor/rules/srvkp-jira-bug-template.mdc

@@ -0,0 +1,23 @@
+---
+description: SRVKP Jira Bug Report Template
+alwaysApply: false
+---
+
+# SRVKP Jira Bug Report Template
+
+h3. *Description of problem:*
+
+Workaround
+h3. *Prerequisites (if any, like setup, operators/versions):*
+h3. *Steps to Reproduce*
+
+ # <steps>
+
+h3. *Actual results:*
+h3. *Expected results:*
+h3. *Reproducibility (Always/Intermittent/Only Once):*
+h3. *Acceptance criteria:*
+
+*Definition of Done:*
+h3. *Build Details:*
+h3. *Additional info (Such as Logs, Screenshots, etc):*

.cursor/rules/srvkp-jira-template.mdc

@@ -0,0 +1,66 @@
+---
+description: SRVKP Jira Ticket Template
+alwaysApply: false
+---
+
+# SRVKP Jira Ticket Template
+
+h1. Story (Required)
+
+As a <PERSONA> trying to <ACTION> I want <THIS OUTCOME>
+
+_<Describes high level purpose and goal for this story. Answers the questions: Who is impacted, what is it and why do we need it? How does it improve the customer’s experience?>_
+
+h2. *Background (Required)*
+
+_<Describes the context or background related to this story>_
+
+h2. *Out of scope*
+
+_<Defines what is not included in this story>_
+
+h2. *Approach (Required)*
+
+_<Description of the general technical path on how to achieve the goal of the story. Include details like json schema, class definitions>_
+
+h2. *Dependencies*
+
+_<Describes what this story depends on. Dependent Stories and EPICs should be linked to the story.>_
+
+h2. *Acceptance Criteria (Mandatory)*
+
+_<Describe edge cases to consider when implementing the story and defining tests>_
+
+_<Provides a required and minimum list of acceptance tests for this story. More is expected as the engineer implements this story>_
+
+h1. *INVEST Checklist*
+
+Dependencies identified
+
+Blockers noted and expected delivery timelines set
+
+Design is implementable
+
+Acceptance criteria agreed upon
+
+Story estimated
+
+h4. *Legend*
+
+Unknown
+
+Verified
+
+Unsatisfied
+
+h2. *Done Checklist*
+
+* Code is completed, reviewed, documented and checked in
+
+* Unit and integration test automation have been delivered and running cleanly in continuous integration/staging/canary environment
+
+* Continuous Delivery pipeline(s) is able to proceed with new code included
+
+* Customer facing documentation, API docs etc. are produced/updated, reviewed and published
+
+* Acceptance criteria are met