Generate Pelican site

kiwitcms · Aug 14, 2024 · 8c25aaa · 8c25aaa
1 parent 35c0172
commit 8c25aaa
Show file tree

Hide file tree

Showing 6 changed files with 18 additions and 6 deletions.
diff --git a/blog/index.html b/blog/index.html
@@ -1322,7 +1322,9 @@ <h1 class="top-header">Feature showcase: Personal API tokens</h1>
 <img alt="&quot;Navigate to Personal API tokens in Kiwi TCMS&quot;" src="/images/features/personal-api-tokens/step_008.png" title="Navigate to Personal API tokens in Kiwi TCMS"></p>
 </li>
 <li>
-<p>Select an existing Issue Tracker via its URL and fill-in your credentials. For JIRA
+<p>Select an existing Issue Tracker via its URL and fill-in your credentials. The drop-down choices
+  represent all Issue Tracker records accessible to the current user across all tenants they are
+  authorized for! For JIRA
   <code>api_username</code> is your JIRA email and <code>api_password</code> is your JIRA API token.
   Other issue trackers may only require the <code>api_password</code> field. The meaning of
   these fields can be found in

diff --git a/blog/kiwi-tcms-team/2023/12/06/feature-showcase-personal-api-tokens/index.html b/blog/kiwi-tcms-team/2023/12/06/feature-showcase-personal-api-tokens/index.html
@@ -173,7 +173,9 @@ <h2 class="top-subheader">available in Kiwi TCMS v12.7 Private Tenant & Enterpri
 <img alt="&quot;Navigate to Personal API tokens in Kiwi TCMS&quot;" src="/images/features/personal-api-tokens/step_008.png" title="Navigate to Personal API tokens in Kiwi TCMS"></p>
 </li>
 <li>
-<p>Select an existing Issue Tracker via its URL and fill-in your credentials. For JIRA
+<p>Select an existing Issue Tracker via its URL and fill-in your credentials. The drop-down choices
+  represent all Issue Tracker records accessible to the current user across all tenants they are
+  authorized for! For JIRA
   <code>api_username</code> is your JIRA email and <code>api_password</code> is your JIRA API token.
   Other issue trackers may only require the <code>api_password</code> field. The meaning of
   these fields can be found in

diff --git a/blog/kiwi-tcms-team/index.html b/blog/kiwi-tcms-team/index.html
@@ -1328,7 +1328,9 @@ <h1 class="top-header">Feature showcase: Personal API tokens</h1>
 <img alt="&quot;Navigate to Personal API tokens in Kiwi TCMS&quot;" src="/images/features/personal-api-tokens/step_008.png" title="Navigate to Personal API tokens in Kiwi TCMS"></p>
 </li>
 <li>
-<p>Select an existing Issue Tracker via its URL and fill-in your credentials. For JIRA
+<p>Select an existing Issue Tracker via its URL and fill-in your credentials. The drop-down choices
+  represent all Issue Tracker records accessible to the current user across all tenants they are
+  authorized for! For JIRA
   <code>api_username</code> is your JIRA email and <code>api_password</code> is your JIRA API token.
   Other issue trackers may only require the <code>api_password</code> field. The meaning of
   these fields can be found in

diff --git a/blog/tags/features/index.html b/blog/tags/features/index.html
@@ -153,7 +153,9 @@ <h1 class="top-header">Feature showcase: Personal API tokens</h1>
 <img alt="&quot;Navigate to Personal API tokens in Kiwi TCMS&quot;" src="/images/features/personal-api-tokens/step_008.png" title="Navigate to Personal API tokens in Kiwi TCMS"></p>
 </li>
 <li>
-<p>Select an existing Issue Tracker via its URL and fill-in your credentials. For JIRA
+<p>Select an existing Issue Tracker via its URL and fill-in your credentials. The drop-down choices
+  represent all Issue Tracker records accessible to the current user across all tenants they are
+  authorized for! For JIRA
   <code>api_username</code> is your JIRA email and <code>api_password</code> is your JIRA API token.
   Other issue trackers may only require the <code>api_password</code> field. The meaning of
   these fields can be found in

diff --git a/feeds/all.atom.xml b/feeds/all.atom.xml
@@ -1188,7 +1188,9 @@ issue tracker configurations with their own API credentials. Here's how it works
 &lt;img alt="&amp;quot;Navigate to Personal API tokens in Kiwi TCMS&amp;quot;" src="/images/features/personal-api-tokens/step_008.png" title="Navigate to Personal API tokens in Kiwi TCMS"&gt;&lt;/p&gt;
 &lt;/li&gt;
 &lt;li&gt;
-&lt;p&gt;Select an existing Issue Tracker via its URL and fill-in your credentials. For JIRA
+&lt;p&gt;Select an existing Issue Tracker via its URL and fill-in your credentials. The drop-down choices
+  represent all Issue Tracker records accessible to the current user across all tenants they are
+  authorized for! For JIRA
   &lt;code&gt;api_username&lt;/code&gt; is your JIRA email and &lt;code&gt;api_password&lt;/code&gt; is your JIRA API token.
   Other issue trackers may only require the &lt;code&gt;api_password&lt;/code&gt; field. The meaning of
   these fields can be found in

diff --git a/feeds/misc.atom.xml b/feeds/misc.atom.xml
@@ -1188,7 +1188,9 @@ issue tracker configurations with their own API credentials. Here's how it works
 &lt;img alt="&amp;quot;Navigate to Personal API tokens in Kiwi TCMS&amp;quot;" src="/images/features/personal-api-tokens/step_008.png" title="Navigate to Personal API tokens in Kiwi TCMS"&gt;&lt;/p&gt;
 &lt;/li&gt;
 &lt;li&gt;
-&lt;p&gt;Select an existing Issue Tracker via its URL and fill-in your credentials. For JIRA
+&lt;p&gt;Select an existing Issue Tracker via its URL and fill-in your credentials. The drop-down choices
+  represent all Issue Tracker records accessible to the current user across all tenants they are
+  authorized for! For JIRA
   &lt;code&gt;api_username&lt;/code&gt; is your JIRA email and &lt;code&gt;api_password&lt;/code&gt; is your JIRA API token.
   Other issue trackers may only require the &lt;code&gt;api_password&lt;/code&gt; field. The meaning of
   these fields can be found in