Update wiki Home page for jira-transition-issue-sink

Home.md

@@ -1,21 +1,40 @@
-# Deploy the Project on CamelX Platform
+# Jira Transition Issue Sink
 
-Deploy on CamelX Platform in three steps
+Sets a new status (transition to) of an existing issue in Jira.
 
-## Step 1: Create a release
+The Kamelet expects the following headers to be set:
-From the project space, click on **"Create a release"**
 
-The new version is automatically available in the list
+- `issueKey` / `ce-issueKey`: as the issue unique code.
 
-## Step 2: Deploy
+- `issueTransitionId` / `ce-issueTransitionId`: as the new status (transition) code. You should carefully check the project workflow as each transition may have conditions to check before the transition is made.
-Click on **"Deploy"**
 
-- **Version:** Select the desired release
+The comment of the transition is set in the body of the message.
-- **Environment:** Choose `Development`, `Staging`, or `Production` 
-- **Configuration:** Select the configuration source
-- **Resources:** Set CPU and Memory
 
-## Step 3: Expose
+To authenticate a username/password or personal token must be defined. We recommend to use personal token as it is a safer way to get access to Jira.
-Enable **"Expose"**
 
-Choose an **API Gateway** (Internal, Public, etc.)
+## Metadata
+
+| Property | Value |
+|----------|-------|
+| Type | sink |
+| Group | JIRA |
+| Namespace | JIRA |
+| Support Level | Stable |
+| Provider | Apache Software Foundation |
+
+## Properties
+
+| Name | Type | Required | Default | Description |
+|------|------|----------|---------|-------------|
+| `jiraUrl` | string | ✓ |  | The URL of your instance of Jira |
+| `username` | string |  |  | The username to access Jira |
+| `password` | string |  |  | The password to access Jira |
+| `personal-token` | string |  |  | Personal Token |
+
+## Dependencies
+
+- `camel:core`
+- `camel:jackson`
+- `camel:jira`
+- `camel:kamelet`
+- `mvn:com.fasterxml.jackson.datatype:jackson-datatype-joda:2.12.5`