atlassian-modules 0.3__tar.gz → 0.4__tar.gz

{atlassian_modules-0.3 → atlassian_modules-0.4}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.1
 Name: atlassian_modules
-Version: 0.3
+Version: 0.4
 Summary: Modules for interacting with Atlassian products.
 Home-page: 
 Author: Pavan Bhatt
@@ -56,7 +56,68 @@ Return:
 - `URL of the created ticket (str)`: If the ticket creation is successful, the function returns the URL to access the newly created ticket directly. 
 - `False`: If the ticket creation fails (for example, due to incorrect input parameters or server errors), the function returns `False`.
 ______________________________________________________________________________
-## 2. Delete a Jira Ticket
+## 2. Create a custom Jira Ticket
+- You can create a new custom Jira ticket using the `create_custom_ticket` method:
+
+```python
+jira_helper = JiraHelper(JIRA_URL, EMAIL, API_TOKEN)
+
+# Define additional fields if necessary
+additional_fields = {
+    "customfield_12345": "Custom value",
+    "labels": ["label1", "label2"]
+}
+
+ticket_url = jira_helper.create_custom_ticket("PRJ", "Issue Summary", "Detailed issue description.", "Bug", additional_fields)
+if ticket_url:
+    print(f"Ticket created: {ticket_url}")
+else:
+    print("Failed to create ticket.")
+
+```
+Parameters:
+- `project_key` (str): The key of the project where the new ticket will be created. This is typically a short, capitalized identifier specific to a project in Jira. 
+- `summary` (str): A concise overview of the issue or task that the new ticket will represent. 
+- `description` (str): A detailed description of the issue or task, providing all necessary details for understanding and addressing it. 
+- `issue_type` (str): Specifies the type of issue being created (e.g., `Bug`, `Task`, `Story`), determining how the issue is categorized within Jira. 
+- `additional_fields` (dict, optional): A dictionary of additional fields that are required for ticket creation. This parameter allows for the inclusion of project-specific or issue-specific information that is not covered by the standard fields.
+
+Output:
+- The function provides informational messages throughout the process of creating a ticket.
+- These messages include details on preparing the issue data, sending a request to create the ticket, and the outcome of that request.
+Return:
+- `URL of the created ticket` (str): If the ticket creation is successful, the function returns the URL to access the newly created ticket directly. This allows for immediate navigation to the ticket for review or further action.
+- `False`: If the ticket creation process fails, whether due to incorrect input parameters, server errors, or issues with the additional fields, the function returns `False`. This indicates that the ticket was not created and provides an opportunity to address any issues before retrying.
+______________________________________________________________________________
+## 3. Update the Jira ticket with inbuilt and custom fields
+- You can update any custom field of Jira ticket using the `update_ticket_with_fields` method:
+```python
+jira_helper = JiraHelper(JIRA_URL, EMAIL, API_TOKEN)
+
+# Define the additional fields you want to update
+additional_fields = {
+    "customfield_12345": "New custom value",
+    "labels": ["newlabel1", "newlabel2"]
+}
+
+ticket_id = "PRJ-123"  # Example ticket ID to be updated
+
+update_success = jira_helper.update_ticket_with_fields(ticket_id, additional_fields)
+if update_success:
+    print(f"Ticket {ticket_id} updated successfully.")
+else:
+    print(f"Failed to update ticket {ticket_id}.")
+```
+Parameters:
+- `ticket_id` (str): ID (also known as the key) of the ticket to be updated. This identifier is typically a combination of the project key and a sequence number, like `PRJ-123`. 
+- `additional_fields` (dict): A dictionary of fields to update the ticket with. This parameter allows specifying values for any standard or custom field in the ticket that supports updates.
+Output:
+- The function prints messages about the process of updating the ticket, including preparing the update data, making the request to update the ticket, and the result of that request.
+Return:
+- `True` if the update was successful. This indicates that the server accepted the update request and applied the changes to the ticket. 
+- `False` otherwise. If the ticket update fails (for example, due to incorrect ticket ID, fields that cannot be updated, or server errors), the function returns `False`, and additional error information is printed to help diagnose the issue.
+______________________________________________________________________________
+## 3. Delete a Jira Ticket
 
 - To delete a ticket, use the `delete_ticket` method:
 
@@ -79,7 +140,7 @@ Return:
 - `True`: If the ticket is successfully deleted. This is indicated by a `204` HTTP status code from the JIRA API, meaning "`No Content`" but signifying successful deletion. 
 - `False`: If the deletion fails, which can occur if the ticket does not exist or if there's an issue with the API request (e.g., permissions, invalid ticket key). This is communicated by returning `False`.
 ______________________________________________________________________________
-## 3. Get Transition ID
+## 4. Get Transition ID
 
 ```python
 jira_helper = JiraHelper(JIRA_URL, EMAIL, API_TOKEN)
@@ -104,7 +165,7 @@ Return:
 - `Transition ID` (str): If the specified transition is found for the given ticket, the function returns the transition's ID, which can be used for further actions like transitioning the ticket to another status.
 - `False`: If the specified transition is not found for the ticket, or if there is any failure in fetching transitions (e.g., due to an invalid ticket key, network issues, or server errors), the function returns `False`.
 ______________________________________________________________________________
-## 4. Transition a Jira Ticket
+## 5. Transition a Jira Ticket
 
 - To transition a ticket to a different status, use the `transition_ticket` method:
 
@@ -131,7 +192,7 @@ Return:
 - `False`: If the ticket transition fails. This could be due to various reasons, such as an invalid ticket key, an unrecognized transition name or ID, or a failure in the HTTP request itself.
 
 ______________________________________________________________________________
-## 5. If exist a Jira Ticket
+## 6. If exist a Jira Ticket
 
 - To check if a ticket exist, use the `if_ticket_exist` method:
 
@@ -154,7 +215,7 @@ Return:
 - `True`: If the ticket exists. This is confirmed by a `200` HTTP status code, indicating that the ticket was found. 
 - `False`: If the ticket does not exist or if there was an error in checking. A `404` HTTP status code indicates the ticket does not exist. Other status codes indicate a failure in the request to check the ticket.
 ______________________________________________________________________________
-## 6. Comment on a Jira ticket
+## 7. Comment on a Jira ticket
 
 - To comment on the ticket, use the `comment_ticket` method:
 
@@ -180,7 +241,7 @@ Return:
 - `URL of the created comment` (str): If adding the comment is successful, the function returns the URL to access the newly created comment directly. This is indicated by a `201` HTTP status code, meaning "`Created`". 
 - `False`: If adding the comment fails. This could be because the ticket does not exist, the comment text is invalid, or there was an error in the request itself. In such cases, the function returns `False`.
 ______________________________________________________________________________
-## 7. Pass the JQL and get the ticket array
+## 8. Pass the JQL and get the ticket array
 
 - To query tickets using JQL, use the `jql_ticket` method:
 
@@ -554,12 +615,19 @@ ______________________________________________________________________________
 
 # Release Notes
 
-## Latest Release: 0.3 (21 Mar 2024)
-- Enhancements:
-  - Updated `readme.md` documentation. 
-  - Introduced beta functions `wiki_helper.add_row_to_table` & `wiki_helper.update_or_add_table_row` for improved table management.
+## Latest Release: 0.4 (21 Mar 2024)
+- New Features:
+  - JIRA Integration Enhancements:
+    - Custom Ticket Creation: The `create_custom_ticket` function has been introduced, allowing for more flexible ticket creation in JIRA projects. This function supports additional fields, enabling users to specify custom data during ticket creation. 
+    - Ticket Field Updates: The `update_ticket_with_fields` method has been added, offering the ability to update existing tickets with new or modified fields. This feature is crucial for maintaining accurate and up-to-date ticket information.
+- Beta Features (Continued from previous release):
+  - Beta functions `wiki_helper.add_row_to_table` & `wiki_helper.update_or_add_table_row` for improved table management.
 
 ## Previous Releases:
+- 0.3 (21 Mar 2024)
+  - Enhancements:
+    - Updated `readme.md` documentation. 
+    - Introduced beta functions `wiki_helper.add_row_to_table` & `wiki_helper.update_or_add_table_row` for improved table management.
 - 0.2.8 (21 Mar 2024)
   - Minor updates and enhancements (details forthcoming).
 - 0.2.7 (08 Jan 2024)

{atlassian_modules-0.3 → atlassian_modules-0.4}/README.md

@@ -47,7 +47,68 @@ Return:
 - `URL of the created ticket (str)`: If the ticket creation is successful, the function returns the URL to access the newly created ticket directly. 
 - `False`: If the ticket creation fails (for example, due to incorrect input parameters or server errors), the function returns `False`.
 ______________________________________________________________________________
-## 2. Delete a Jira Ticket
+## 2. Create a custom Jira Ticket
+- You can create a new custom Jira ticket using the `create_custom_ticket` method:
+
+```python
+jira_helper = JiraHelper(JIRA_URL, EMAIL, API_TOKEN)
+
+# Define additional fields if necessary
+additional_fields = {
+    "customfield_12345": "Custom value",
+    "labels": ["label1", "label2"]
+}
+
+ticket_url = jira_helper.create_custom_ticket("PRJ", "Issue Summary", "Detailed issue description.", "Bug", additional_fields)
+if ticket_url:
+    print(f"Ticket created: {ticket_url}")
+else:
+    print("Failed to create ticket.")
+
+```
+Parameters:
+- `project_key` (str): The key of the project where the new ticket will be created. This is typically a short, capitalized identifier specific to a project in Jira. 
+- `summary` (str): A concise overview of the issue or task that the new ticket will represent. 
+- `description` (str): A detailed description of the issue or task, providing all necessary details for understanding and addressing it. 
+- `issue_type` (str): Specifies the type of issue being created (e.g., `Bug`, `Task`, `Story`), determining how the issue is categorized within Jira. 
+- `additional_fields` (dict, optional): A dictionary of additional fields that are required for ticket creation. This parameter allows for the inclusion of project-specific or issue-specific information that is not covered by the standard fields.
+
+Output:
+- The function provides informational messages throughout the process of creating a ticket.
+- These messages include details on preparing the issue data, sending a request to create the ticket, and the outcome of that request.
+Return:
+- `URL of the created ticket` (str): If the ticket creation is successful, the function returns the URL to access the newly created ticket directly. This allows for immediate navigation to the ticket for review or further action.
+- `False`: If the ticket creation process fails, whether due to incorrect input parameters, server errors, or issues with the additional fields, the function returns `False`. This indicates that the ticket was not created and provides an opportunity to address any issues before retrying.
+______________________________________________________________________________
+## 3. Update the Jira ticket with inbuilt and custom fields
+- You can update any custom field of Jira ticket using the `update_ticket_with_fields` method:
+```python
+jira_helper = JiraHelper(JIRA_URL, EMAIL, API_TOKEN)
+
+# Define the additional fields you want to update
+additional_fields = {
+    "customfield_12345": "New custom value",
+    "labels": ["newlabel1", "newlabel2"]
+}
+
+ticket_id = "PRJ-123"  # Example ticket ID to be updated
+
+update_success = jira_helper.update_ticket_with_fields(ticket_id, additional_fields)
+if update_success:
+    print(f"Ticket {ticket_id} updated successfully.")
+else:
+    print(f"Failed to update ticket {ticket_id}.")
+```
+Parameters:
+- `ticket_id` (str): ID (also known as the key) of the ticket to be updated. This identifier is typically a combination of the project key and a sequence number, like `PRJ-123`. 
+- `additional_fields` (dict): A dictionary of fields to update the ticket with. This parameter allows specifying values for any standard or custom field in the ticket that supports updates.
+Output:
+- The function prints messages about the process of updating the ticket, including preparing the update data, making the request to update the ticket, and the result of that request.
+Return:
+- `True` if the update was successful. This indicates that the server accepted the update request and applied the changes to the ticket. 
+- `False` otherwise. If the ticket update fails (for example, due to incorrect ticket ID, fields that cannot be updated, or server errors), the function returns `False`, and additional error information is printed to help diagnose the issue.
+______________________________________________________________________________
+## 3. Delete a Jira Ticket
 
 - To delete a ticket, use the `delete_ticket` method:
 
@@ -70,7 +131,7 @@ Return:
 - `True`: If the ticket is successfully deleted. This is indicated by a `204` HTTP status code from the JIRA API, meaning "`No Content`" but signifying successful deletion. 
 - `False`: If the deletion fails, which can occur if the ticket does not exist or if there's an issue with the API request (e.g., permissions, invalid ticket key). This is communicated by returning `False`.
 ______________________________________________________________________________
-## 3. Get Transition ID
+## 4. Get Transition ID
 
 ```python
 jira_helper = JiraHelper(JIRA_URL, EMAIL, API_TOKEN)
@@ -95,7 +156,7 @@ Return:
 - `Transition ID` (str): If the specified transition is found for the given ticket, the function returns the transition's ID, which can be used for further actions like transitioning the ticket to another status.
 - `False`: If the specified transition is not found for the ticket, or if there is any failure in fetching transitions (e.g., due to an invalid ticket key, network issues, or server errors), the function returns `False`.
 ______________________________________________________________________________
-## 4. Transition a Jira Ticket
+## 5. Transition a Jira Ticket
 
 - To transition a ticket to a different status, use the `transition_ticket` method:
 
@@ -122,7 +183,7 @@ Return:
 - `False`: If the ticket transition fails. This could be due to various reasons, such as an invalid ticket key, an unrecognized transition name or ID, or a failure in the HTTP request itself.
 
 ______________________________________________________________________________
-## 5. If exist a Jira Ticket
+## 6. If exist a Jira Ticket
 
 - To check if a ticket exist, use the `if_ticket_exist` method:
 
@@ -145,7 +206,7 @@ Return:
 - `True`: If the ticket exists. This is confirmed by a `200` HTTP status code, indicating that the ticket was found. 
 - `False`: If the ticket does not exist or if there was an error in checking. A `404` HTTP status code indicates the ticket does not exist. Other status codes indicate a failure in the request to check the ticket.
 ______________________________________________________________________________
-## 6. Comment on a Jira ticket
+## 7. Comment on a Jira ticket
 
 - To comment on the ticket, use the `comment_ticket` method:
 
@@ -171,7 +232,7 @@ Return:
 - `URL of the created comment` (str): If adding the comment is successful, the function returns the URL to access the newly created comment directly. This is indicated by a `201` HTTP status code, meaning "`Created`". 
 - `False`: If adding the comment fails. This could be because the ticket does not exist, the comment text is invalid, or there was an error in the request itself. In such cases, the function returns `False`.
 ______________________________________________________________________________
-## 7. Pass the JQL and get the ticket array
+## 8. Pass the JQL and get the ticket array
 
 - To query tickets using JQL, use the `jql_ticket` method:
 
@@ -545,12 +606,19 @@ ______________________________________________________________________________
 
 # Release Notes
 
-## Latest Release: 0.3 (21 Mar 2024)
-- Enhancements:
-  - Updated `readme.md` documentation. 
-  - Introduced beta functions `wiki_helper.add_row_to_table` & `wiki_helper.update_or_add_table_row` for improved table management.
+## Latest Release: 0.4 (21 Mar 2024)
+- New Features:
+  - JIRA Integration Enhancements:
+    - Custom Ticket Creation: The `create_custom_ticket` function has been introduced, allowing for more flexible ticket creation in JIRA projects. This function supports additional fields, enabling users to specify custom data during ticket creation. 
+    - Ticket Field Updates: The `update_ticket_with_fields` method has been added, offering the ability to update existing tickets with new or modified fields. This feature is crucial for maintaining accurate and up-to-date ticket information.
+- Beta Features (Continued from previous release):
+  - Beta functions `wiki_helper.add_row_to_table` & `wiki_helper.update_or_add_table_row` for improved table management.
 
 ## Previous Releases:
+- 0.3 (21 Mar 2024)
+  - Enhancements:
+    - Updated `readme.md` documentation. 
+    - Introduced beta functions `wiki_helper.add_row_to_table` & `wiki_helper.update_or_add_table_row` for improved table management.
 - 0.2.8 (21 Mar 2024)
   - Minor updates and enhancements (details forthcoming).
 - 0.2.7 (08 Jan 2024)

{atlassian_modules-0.3 → atlassian_modules-0.4}/atlassian_modules/helper.py

@@ -11,6 +11,87 @@ class JiraHelper:
             "Content-Type": "application/json"
         }
 
+    def create_custom_ticket(self, project_key, summary, description, issue_type, additional_fields=None):
+        """
+        Create a ticket in a specified project using the provided details and additional fields.
+
+        :param project_key: Key of the project where the new ticket will be created.
+        :param summary: Summary of the new ticket.
+        :param description: Detailed description of the new ticket.
+        :param issue_type: Type of the issue (e.g., Bug, Task, Story).
+        :param additional_fields: Dictionary of additional fields required for ticket creation.
+        :return: URL of the created ticket or False if the creation failed.
+        """
+        # Preparing issue data
+        print("Preparing issue data...")
+        issue_data = {
+            "fields": {
+                "project": {"key": project_key},
+                "summary": summary,
+                "description": description,
+                "issuetype": {"name": issue_type},
+            }
+        }
+
+        # Incorporating additional fields if provided
+        if additional_fields:
+            issue_data["fields"].update(additional_fields)
+
+        # Making a request to create a ticket
+        print(f"Sending request to create a ticket in project {project_key}...")
+        response = requests.post(
+            f"{self.server_url}/rest/api/2/issue",
+            json=issue_data,
+            headers=self.headers,
+            auth=self.auth
+        )
+
+        # Checking response
+        if response.status_code == 201:  # HTTP 201 Created
+            print("Ticket created successfully!")
+            ticket_data = response.json()
+            ticket_key = ticket_data["key"]
+            ticket_url = f"{self.server_url}/browse/{ticket_key}"
+            print(f"Ticket URL: {ticket_url}")
+            return ticket_url
+        else:
+            print(f"Failed to create ticket. HTTP Status Code: {response.status_code}")
+            print(f"Response Content: {response.text}")
+            return False
+
+    def update_ticket_with_fields(self, ticket_id, additional_fields):
+        """
+        Update a JIRA ticket with additional fields.
+
+        :param ticket_id: ID (key) of the ticket to be updated.
+        :param additional_fields: Dictionary of fields to update the ticket with.
+        :return: True if the update was successful, False otherwise.
+        """
+        print(f"Updating ticket {ticket_id} with additional fields...")
+
+        # Preparing the update data
+        update_data = {
+            "fields": additional_fields
+        }
+
+        # Making a request to update the ticket
+        print(f"Sending request to update ticket {ticket_id}...")
+        response = requests.put(
+            f"{self.server_url}/rest/api/2/issue/{ticket_id}",
+            json=update_data,
+            headers=self.headers,
+            auth=self.auth
+        )
+
+        # Checking response
+        if response.status_code in [200, 204]:  # HTTP 200 OK or 204 No Content indicate success
+            print("Ticket updated successfully!")
+            return True
+        else:
+            print(f"Failed to update ticket. HTTP Status Code: {response.status_code}")
+            print(f"Response Content: {response.text}")
+            return False
+
     def create_ticket(self, project_key, summary, description, issue_type):
         """
         Create a ticket in a specified project using the provided details.

{atlassian_modules-0.3 → atlassian_modules-0.4}/atlassian_modules.egg-info/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.1
 Name: atlassian-modules
-Version: 0.3
+Version: 0.4
 Summary: Modules for interacting with Atlassian products.
 Home-page: 
 Author: Pavan Bhatt
@@ -56,7 +56,68 @@ Return:
 - `URL of the created ticket (str)`: If the ticket creation is successful, the function returns the URL to access the newly created ticket directly. 
 - `False`: If the ticket creation fails (for example, due to incorrect input parameters or server errors), the function returns `False`.
 ______________________________________________________________________________
-## 2. Delete a Jira Ticket
+## 2. Create a custom Jira Ticket
+- You can create a new custom Jira ticket using the `create_custom_ticket` method:
+
+```python
+jira_helper = JiraHelper(JIRA_URL, EMAIL, API_TOKEN)
+
+# Define additional fields if necessary
+additional_fields = {
+    "customfield_12345": "Custom value",
+    "labels": ["label1", "label2"]
+}
+
+ticket_url = jira_helper.create_custom_ticket("PRJ", "Issue Summary", "Detailed issue description.", "Bug", additional_fields)
+if ticket_url:
+    print(f"Ticket created: {ticket_url}")
+else:
+    print("Failed to create ticket.")
+
+```
+Parameters:
+- `project_key` (str): The key of the project where the new ticket will be created. This is typically a short, capitalized identifier specific to a project in Jira. 
+- `summary` (str): A concise overview of the issue or task that the new ticket will represent. 
+- `description` (str): A detailed description of the issue or task, providing all necessary details for understanding and addressing it. 
+- `issue_type` (str): Specifies the type of issue being created (e.g., `Bug`, `Task`, `Story`), determining how the issue is categorized within Jira. 
+- `additional_fields` (dict, optional): A dictionary of additional fields that are required for ticket creation. This parameter allows for the inclusion of project-specific or issue-specific information that is not covered by the standard fields.
+
+Output:
+- The function provides informational messages throughout the process of creating a ticket.
+- These messages include details on preparing the issue data, sending a request to create the ticket, and the outcome of that request.
+Return:
+- `URL of the created ticket` (str): If the ticket creation is successful, the function returns the URL to access the newly created ticket directly. This allows for immediate navigation to the ticket for review or further action.
+- `False`: If the ticket creation process fails, whether due to incorrect input parameters, server errors, or issues with the additional fields, the function returns `False`. This indicates that the ticket was not created and provides an opportunity to address any issues before retrying.
+______________________________________________________________________________
+## 3. Update the Jira ticket with inbuilt and custom fields
+- You can update any custom field of Jira ticket using the `update_ticket_with_fields` method:
+```python
+jira_helper = JiraHelper(JIRA_URL, EMAIL, API_TOKEN)
+
+# Define the additional fields you want to update
+additional_fields = {
+    "customfield_12345": "New custom value",
+    "labels": ["newlabel1", "newlabel2"]
+}
+
+ticket_id = "PRJ-123"  # Example ticket ID to be updated
+
+update_success = jira_helper.update_ticket_with_fields(ticket_id, additional_fields)
+if update_success:
+    print(f"Ticket {ticket_id} updated successfully.")
+else:
+    print(f"Failed to update ticket {ticket_id}.")
+```
+Parameters:
+- `ticket_id` (str): ID (also known as the key) of the ticket to be updated. This identifier is typically a combination of the project key and a sequence number, like `PRJ-123`. 
+- `additional_fields` (dict): A dictionary of fields to update the ticket with. This parameter allows specifying values for any standard or custom field in the ticket that supports updates.
+Output:
+- The function prints messages about the process of updating the ticket, including preparing the update data, making the request to update the ticket, and the result of that request.
+Return:
+- `True` if the update was successful. This indicates that the server accepted the update request and applied the changes to the ticket. 
+- `False` otherwise. If the ticket update fails (for example, due to incorrect ticket ID, fields that cannot be updated, or server errors), the function returns `False`, and additional error information is printed to help diagnose the issue.
+______________________________________________________________________________
+## 3. Delete a Jira Ticket
 
 - To delete a ticket, use the `delete_ticket` method:
 
@@ -79,7 +140,7 @@ Return:
 - `True`: If the ticket is successfully deleted. This is indicated by a `204` HTTP status code from the JIRA API, meaning "`No Content`" but signifying successful deletion. 
 - `False`: If the deletion fails, which can occur if the ticket does not exist or if there's an issue with the API request (e.g., permissions, invalid ticket key). This is communicated by returning `False`.
 ______________________________________________________________________________
-## 3. Get Transition ID
+## 4. Get Transition ID
 
 ```python
 jira_helper = JiraHelper(JIRA_URL, EMAIL, API_TOKEN)
@@ -104,7 +165,7 @@ Return:
 - `Transition ID` (str): If the specified transition is found for the given ticket, the function returns the transition's ID, which can be used for further actions like transitioning the ticket to another status.
 - `False`: If the specified transition is not found for the ticket, or if there is any failure in fetching transitions (e.g., due to an invalid ticket key, network issues, or server errors), the function returns `False`.
 ______________________________________________________________________________
-## 4. Transition a Jira Ticket
+## 5. Transition a Jira Ticket
 
 - To transition a ticket to a different status, use the `transition_ticket` method:
 
@@ -131,7 +192,7 @@ Return:
 - `False`: If the ticket transition fails. This could be due to various reasons, such as an invalid ticket key, an unrecognized transition name or ID, or a failure in the HTTP request itself.
 
 ______________________________________________________________________________
-## 5. If exist a Jira Ticket
+## 6. If exist a Jira Ticket
 
 - To check if a ticket exist, use the `if_ticket_exist` method:
 
@@ -154,7 +215,7 @@ Return:
 - `True`: If the ticket exists. This is confirmed by a `200` HTTP status code, indicating that the ticket was found. 
 - `False`: If the ticket does not exist or if there was an error in checking. A `404` HTTP status code indicates the ticket does not exist. Other status codes indicate a failure in the request to check the ticket.
 ______________________________________________________________________________
-## 6. Comment on a Jira ticket
+## 7. Comment on a Jira ticket
 
 - To comment on the ticket, use the `comment_ticket` method:
 
@@ -180,7 +241,7 @@ Return:
 - `URL of the created comment` (str): If adding the comment is successful, the function returns the URL to access the newly created comment directly. This is indicated by a `201` HTTP status code, meaning "`Created`". 
 - `False`: If adding the comment fails. This could be because the ticket does not exist, the comment text is invalid, or there was an error in the request itself. In such cases, the function returns `False`.
 ______________________________________________________________________________
-## 7. Pass the JQL and get the ticket array
+## 8. Pass the JQL and get the ticket array
 
 - To query tickets using JQL, use the `jql_ticket` method:
 
@@ -554,12 +615,19 @@ ______________________________________________________________________________
 
 # Release Notes
 
-## Latest Release: 0.3 (21 Mar 2024)
-- Enhancements:
-  - Updated `readme.md` documentation. 
-  - Introduced beta functions `wiki_helper.add_row_to_table` & `wiki_helper.update_or_add_table_row` for improved table management.
+## Latest Release: 0.4 (21 Mar 2024)
+- New Features:
+  - JIRA Integration Enhancements:
+    - Custom Ticket Creation: The `create_custom_ticket` function has been introduced, allowing for more flexible ticket creation in JIRA projects. This function supports additional fields, enabling users to specify custom data during ticket creation. 
+    - Ticket Field Updates: The `update_ticket_with_fields` method has been added, offering the ability to update existing tickets with new or modified fields. This feature is crucial for maintaining accurate and up-to-date ticket information.
+- Beta Features (Continued from previous release):
+  - Beta functions `wiki_helper.add_row_to_table` & `wiki_helper.update_or_add_table_row` for improved table management.
 
 ## Previous Releases:
+- 0.3 (21 Mar 2024)
+  - Enhancements:
+    - Updated `readme.md` documentation. 
+    - Introduced beta functions `wiki_helper.add_row_to_table` & `wiki_helper.update_or_add_table_row` for improved table management.
 - 0.2.8 (21 Mar 2024)
   - Minor updates and enhancements (details forthcoming).
 - 0.2.7 (08 Jan 2024)

{atlassian_modules-0.3 → atlassian_modules-0.4}/setup.py

@@ -2,7 +2,7 @@ from setuptools import setup, find_packages
 
 setup(
     name="atlassian_modules",
-    version="0.3",
+    version="0.4",
     packages=find_packages(),
     install_requires=[
         "requests",