Jekyll2023-12-14T07:23:28+00:00https://jibrok.com/feed.xmlJiBrokAtlassian Marketplace Partner. Apps for your JiraJiBrokTime in status cloud - Case 1 - simple status time report for a manager2022-06-30T00:00:00+00:002022-06-30T00:00:00+00:00https://jibrok.com/Time%20in%20status%20-%20examples%20of%20using<p>The support team consists of several generalist specialists and a manager. The work is being done in Jira in the SUP project. Every day clients create a large number of issues. Most of these issues are quite typical, not costly in time support for clients. The team’s goals are: promptly solve customer problems, leave customers satisfied with the quality of the service provided.</p>
<p>The work is organized as follows:<br /></p>
<ul>
<li>Every day one of the specialists performs the functions of an employee on duty. He processes new tasks (the “To Do” status): finds out the missing details (and transition it to the “Awaiting for Customer” status), performs primary classification and directs the task to the most competent and least loaded support specialist (transition it to the “In Progress” status);</li>
<li>A support specialist solves the problem. If necessary, he can request the missing information from the client (transition the task to the status “Awaiting for Customer”). When the problem is solved, he moves it to the client to confirm the correctness of the solution (in the status “Review”);</li>
<li>If additional information was requested, the customer can respond and return the task to the duty-person (“To Do” status). If the task is on his review, approve the work (move to the “Done” status), or reject the solution and reopen the task (return to the “To Do” status).</li>
</ul>
<p style="text-align: center;"><a href="/uploads/time-in-status/post/2022-06-30/workflow-for-examples.png"><img src="/uploads/time-in-status/post/2022-06-30/workflow-for-examples.png" style="width:100%" /></a></p>
<p>Roles in the process:</p>
<ul>
<li>Customer</li>
<li>Duty person</li>
<li>Support Specialist</li>
<li>Support Manager</li>
</ul>
<h2 id="case-1-simple-status-time-report-for-a-manager">Case 1: simple status time report for a manager</h2>
<p>Problem: there have been no attempts to estimate which operation takes how long in the described process. Customers complain that the tasks are solved for a very long time. An attempt to calculate the average solution time based on the standard fields Created and Resolved shows that this is true – some tasks are solved for weeks or even months. At the same time, when viewing certain tasks, the data in the history is not so clear. The manager needs a tool that will allow to track the average time for separate stages of the task workflow.</p>
<p>Solution: for each status in the process, we add the Time in Status field. Then, based on these fields, we build a report on the average time for the period</p>
<ol>
<li>Add a new work calendar. In the Apps administration section, in the Time in Status block, select the Calendar tab, click Create. Set the calendar name and working time parameters <a href="/uploads/time-in-status/post/2022-06-30/add-calendar.png"><img src="/uploads/time-in-status/post/2022-06-30/add-calendar.png" style="width:100%" /></a></li>
<li>Add the Time in Status fields for each status (except for the “Done” status, since we are not interested in the amount of time that the task is closed right now).
<ol>
<li>Go to the Time in Status tab, click Create, create fields. <a href="/uploads/time-in-status/post/2022-06-30/field-settings-1.png"><img src="/uploads/time-in-status/post/2022-06-30/field-settings-1.png" style="width:100%" /></a><a href="/uploads/time-in-status/post/2022-06-30/field-settings-2.png"><img src="/uploads/time-in-status/post/2022-06-30/field-settings-2.png" style="width:100%" /></a></li>
<li>We should get something like this: <a href="/uploads/time-in-status/post/2022-06-30/all-fields-settings-1.png"><img src="/uploads/time-in-status/post/2022-06-30/all-fields-settings-1.png" style="width:100%" /></a></li>
</ol>
</li>
<li>Create a desktop with a time report gadget in statuses.
<ol>
<li>Let’s create a dashboard for the manager. <a href="/uploads/time-in-status/post/2022-06-30/dashboard-create-1.png"><img src="/uploads/time-in-status/post/2022-06-30/dashboard-create-1.png" style="width:100%" /></a></li>
<li>Add the gadget Calculated functions for Time in Status to it. <a href="/uploads/time-in-status/post/2022-06-30/dashboard-create-2.png"><img src="/uploads/time-in-status/post/2022-06-30/dashboard-create-2.png" style="width:100%" /></a></li>
<li>On the Config gadget tab, we set up the fields that need to be displayed as lines of our report. <a href="/uploads/time-in-status/post/2022-06-30/dashboard-create-3.png"><img src="/uploads/time-in-status/post/2022-06-30/dashboard-create-3.png" style="width:100%" /></a></li>
<li>Go to the Result tab. <a href="/uploads/time-in-status/post/2022-06-30/dashboard-create-4.png"><img src="/uploads/time-in-status/post/2022-06-30/dashboard-create-4.png" style="width:100%" /></a></li>
</ol>
</li>
<li>Now it can be seen that up to half of the time it takes to solve problems is to clarify the information from customer.</li>
</ol>JiBrokThe support team consists of several generalist specialists and a manager. The work is being done in Jira in the SUP project. Every day clients create a large number of issues. Most of these issues are quite typical, not costly in time support for clients. The team’s goals are: promptly solve customer problems, leave customers satisfied with the quality of the service provided.Calculated custom fields Cloud (JBCF). New Field - Sort by epic rank.2022-06-05T00:00:00+00:002022-06-05T00:00:00+00:00https://jibrok.com/Calculated%20custom%20fields%20Cloud%20(JBCF)%20new%20field:%20Sort%20by%20epic%20rank<p>New Field: Sort by epic rank:<br /></p>
<p style="text-align: center;"><a href="/uploads/jbcf-cloud/sort-by-epic-rank.png"><img src="/uploads/jbcf-cloud/sort-by-epic-rank.png" style="width:75%" /></a></p>
<ul>
<li>Description: The field for sorting tasks by the rank specified in the epic task. When sorting by this field, the tasks in the search results will be after the epic specified in the task. All epics will be sorted by their rank. All tasks from the epic will be under the epic. All tasks under the epic will be sorted by their rank.</li>
<li>Value: String: The field returns the key of the task. On issue screens, adding a field is optional.</li>
<li>Search: The field stores the value in the index.</li>
</ul>JiBrokNew Field: Sort by epic rank: Description: The field for sorting tasks by the rank specified in the epic task. When sorting by this field, the tasks in the search results will be after the epic specified in the task. All epics will be sorted by their rank. All tasks from the epic will be under the epic. All tasks under the epic will be sorted by their rank. Value: String: The field returns the key of the task. On issue screens, adding a field is optional. Search: The field stores the value in the index.New Pricing for the JiBrok Products2022-05-01T00:00:00+00:002022-05-01T00:00:00+00:00https://jibrok.com/New%20pricing<p>During May, we will increase prices for all products and platforms. We are constantly investing in the development of our existing products, their support and the development of new products.</p>
<p>Applications became paid in 2020: <a href="https://jibrok.com/JiBrok-paid-apps/">JiBrok paid apps</a></p>
<p>Over the past couple of years, we have greatly expanded the capabilities of our solutions. This applies both to individual application functions and the platform on which they are available.</p>
<p><strong>Short changelogs and new Apps:</strong></p>
<ul>
<li><a href="https://marketplace.atlassian.com/apps/1220908">Time in status / SLA / Timer / Stopwatch for Jira DC/Cloud</a>
<ul>
<li><a href="https://marketplace.atlassian.com/apps/1220908/time-in-status-sla-timer-stopwatch-for-jira-dc-cloud/version-history">A lot of new features</a></li>
<li>Data center version</li>
<li>Cloud application set
<ul>
<li><a href="https://marketplace.atlassian.com/apps/1220908/time-in-status-sla-timer-stopwatch-for-jira-dc-cloud?hosting=cloud&tab=overview">Time in status for Jira DC/Cloud</a></li>
<li><a href="https://marketplace.atlassian.com/apps/1225685/stopwatch-field?tab=overview&hosting=cloud">Stopwatch field for Jira Cloud</a></li>
<li><a href="https://marketplace.atlassian.com/apps/1225684/timer-field?tab=overview&hosting=cloud">Timer field / SLA for Jira Cloud</a></li>
<li><a href="https://marketplace.atlassian.com/apps/1226143/time-between-dates-for-jira-cloud?tab=overview&hosting=cloud">Time between dates for Jira Cloud</a></li>
<li><a href="https://marketplace.atlassian.com/apps/1227296/user-helper-for-jibrok-cloud-apps?hosting=cloud&tab=overview">User helper for JiBrok cloud apps</a></li>
</ul>
</li>
</ul>
</li>
<li><a href="https://marketplace.atlassian.com/apps/1219615">Message field</a>
<ul>
<li><a href="https://marketplace.atlassian.com/apps/1219615/message-field/version-history">New features</a></li>
<li>Data center version</li>
<li>Cloud version coming soon</li>
</ul>
</li>
<li><a href="https://marketplace.atlassian.com/apps/1223203">Display linked issues</a>
<ul>
<li><a href="https://marketplace.atlassian.com/apps/1223203/display-linked-issues/version-history">New features</a></li>
<li>Data center version</li>
<li>Cloud version</li>
</ul>
</li>
<li><a href="https://marketplace.atlassian.com/apps/1226586/fields-panel-for-jira-service-management-jsm?hosting=cloud&tab=overview">Fields panel for Jira Service Management (JSM)</a>
<ul>
<li>Cloud version</li>
</ul>
</li>
<li><a href="https://marketplace.atlassian.com/apps/1221055">Calculated and other custom fields(JBCF) for Jira DC/Cloud</a>
<ul>
<li><a href="https://marketplace.atlassian.com/apps/1221055/calculated-and-other-custom-fields-jbcf-for-jira-dc-cloud/version-history">New features</a></li>
<li>Data center version</li>
<li>Cloud version</li>
</ul>
</li>
<li>…</li>
</ul>JiBrokDuring May, we will increase prices for all products and platforms. We are constantly investing in the development of our existing products, their support and the development of new products.Timer and Stopwatch custom events2022-02-15T00:00:00+00:002022-02-15T00:00:00+00:00https://jibrok.com/Timer%20custom%20events<p>Custom events became available for timers and stopwatches.
Now with their help you can set up triggers for the timer (start, pause, restart, stop) that will work to a specific change in the field.</p>
<p style="text-align: center;"><a href="/uploads/timer-cloud/customevents/custom-events-menu.png"><img src="/uploads/timer-cloud/customevents/custom-events-menu.png" style="width:100%" /></a></p>
<p>For example, starting a timer when the priority is set to “High”.</p>
<p style="text-align: center;"><a href="/uploads/timer-cloud/customevents/custom-event-to-high-priority.png"><img src="/uploads/timer-cloud/customevents/custom-event-to-high-priority.png" style="width:100%" /></a></p>
<p>Each event contains separate parameters responsible for triggering this event.</p>
<ul>
<li>The field whose value change is to be tracked. It can be any issue field (system field or custom field).</li>
<li>What action should be tracked with this field.
<ul>
<li>Field value changed from ‘value’</li>
<li>Field value changed to ‘value’</li>
<li>The field value has changed from ‘value1’ to ‘value2’.</li>
</ul>
</li>
<li>Field values to trigger the event.</li>
</ul>
<p>Values are set in string representation and have 2 parameters.</p>
<p style="text-align: center;"><a href="/uploads/timer-cloud/customevents/values.png"><img src="/uploads/timer-cloud/customevents/values.png" style="width:100%" /></a></p>
<p>The first parameter (from/to) contains technical information about the value of the field. For example, the id of an option from the select list.</p>
<p>The second parameter (fromString/toString) usually contains readable information about the value of the field. For example, the name of an option from the select list.</p>
<p>The parameter values used are best taken from <a href="https://developer.atlassian.com/cloud/jira/platform/rest/v3/api-group-issues/#api-rest-api-3-issue-issueidorkey-changelog-get">Jira Cloud Rest API - Get changelogs</a> or <a href="https://docs.atlassian.com/software/jira/docs/api/REST/latest//#issue-getIssue">Jira Rest API - get issue - changelog</a></p>
<p>Example from <a href="https://www.postman.com/">Postman</a>:</p>
<p style="text-align: center;"><a href="/uploads/timer-cloud/customevents/rest-changelogs-example.png"><img src="/uploads/timer-cloud/customevents/rest-changelogs-example.png" style="width:100%" /></a></p>
<p>The values obtained with it can be directly inserted into custom events.</p>
<p style="text-align: center;"><a href="/uploads/timer-cloud/customevents/values-2.png"><img src="/uploads/timer-cloud/customevents/values-2.png" style="width:100%" /></a></p>
<p>You can also try to get the required value through the issue history view interface.</p>
<p style="text-align: center;"><a href="/uploads/timer-cloud/customevents/history.png"><img src="/uploads/timer-cloud/customevents/history.png" style="width:100%" /></a></p>
<ul>
<li>If both parameters are left blank, it will be treated as an empty value.</li>
<li>If at least one of the parameters is filled in, then only it will compare.</li>
<li>If both parameters are filled, then both parameters will be compared. Equality on one of them will be enough to trigger the event.
<ul>
<li>Trigger event if (‘to’ equals ‘value from history’) or (‘toString’ equals ‘value from history’).</li>
</ul>
</li>
</ul>
<p>We will soon add this feature to the server/DC version and our other applications.</p>JiBrokCustom events became available for timers and stopwatches. Now with their help you can set up triggers for the timer (start, pause, restart, stop) that will work to a specific change in the field.⭐️ User helper for JiBrok cloud apps - Public release ⭐️2022-01-24T00:00:00+00:002022-01-24T00:00:00+00:00https://jibrok.com/User%20helper%20for%20JiBrok%20cloud%20apps<div>
Today we have published our new free app <a href="https://marketplace.atlassian.com/apps/1227296/user-helper-for-jibrok-cloud-apps?hosting=cloud&tab=overview"> User helper for JiBrok cloud apps <img src="/uploads/user-helper-cloud/user-helper-cloud.png" style="width:24px" /></a>.
<br />
The application will contain dynamic help available to your users about our cloud applications. The documentation is generated based on the settings saved in Jira Cloud, for example custom fields.
<br />
Now the application contains examples of using JQL functions for our applications. In the future, support for new applications, usage examples and use cases.
<br />
<a href="https://jibrok.com/docs/user-helper-cloud/overview/">More info</a>
</div>JiBrokToday we have published our new free app User helper for JiBrok cloud apps . The application will contain dynamic help available to your users about our cloud applications. The documentation is generated based on the settings saved in Jira Cloud, for example custom fields. Now the application contains examples of using JQL functions for our applications. In the future, support for new applications, usage examples and use cases. More infoTimer history display in web panel (Cloud)2022-01-21T00:00:00+00:002022-01-21T00:00:00+00:00https://jibrok.com/Timer%20history%20display%20in%20web%20panel<p>The other day we published improvements that allow you to work with the first launch of the timer. <a href="https://jibrok.com/History-of-restarts-for-the-timer/">More info</a>.
Today we have added a display of the previous timer values in the web panel.</p>
<table>
<tr>
<td><p style="text-align: center;"><a href="/uploads/timer-cloud/timerhistory-1.png"><img src="/uploads/timer-cloud/timerhistory-1.png" style="width:100%" /></a></p></td>
<td><p style="text-align: center;"><a href="/uploads/timer-cloud/timerhistory-2.png"><img src="/uploads/timer-cloud/timerhistory-2.png" style="width:100%" /></a></p></td>
</tr>
</table>
<p>Now, if the timer has a history of restarts, it will be displayed as a panel with access to the history. You can switch back and forth through history. Timers are arranged from new -> to old.</p>
<p>A little later settings for displaying the history will be added to the application admin panel. In particular, history display options.
We are also working on history functionality and will add the ability to account for different goals and timer setting changes.</p>JiBrokThe other day we published improvements that allow you to work with the first launch of the timer. More info. Today we have added a display of the previous timer values in the web panel.History of restarts for the timer (Cloud)2022-01-18T00:00:00+00:002022-01-18T00:00:00+00:00https://jibrok.com/History%20of%20restarts%20for%20the%20timer<p>The timer has a history of previous start-stop-restart cycles.</p>
<p>In the current version, it has several limitations:</p>
<ul>
<li>History is calculated based on current timer settings.</li>
<li>Change of goal is not taken into account in history. The goal is always taken based on the current data in the issue and the timer settings.</li>
</ul>
<p>We do not yet display the history in the interface, this will be in the next releases.
You can get the history of the timer through <a href="https://developer.atlassian.com/cloud/jira/platform/rest/v3/api-group-issue-properties/">JIRA REST API (Issue properties)</a>.</p>
<p>Timer data is stored in properties with the name of your timer.
For example, information about the “TEST TIMER FIELD” timer can be obtained from the following URL: {jira cloud base url}/rest/api/3/issue/{issue key}/properties/TEST TIMER FIELD</p>
<p>The response will be in the following format:
<script src="https://gist.github.com/JiBrok/629f0b84691ffd3d1f9950f14b2a17a7.js"></script></p>
<p>The “history” field lists the previous timers in order. From the first, to the current value.</p>JiBrokThe timer has a history of previous start-stop-restart cycles.New time formats and calendar settings (Cloud)2022-01-18T00:00:00+00:002022-01-18T00:00:00+00:00https://jibrok.com/New%20time%20formats%20and%20calendar%20settings<p>We have added support for new formats for displaying time. Now you can display time converted to minutes/hours/days/weeks/months/years.</p>
<p>Full list of time formats for cloud applications(Time in status, Timer, Stopwatch, Time between dates fields):</p>
<ul>
<li>DEFAULT(“13h 48m”)</li>
<li>D0(“13h 48m 03s”)</li>
<li>D3(“833”)</li>
<li>D4(“833m”)</li>
<li>D5(“13”)</li>
<li>D6(“13h”)</li>
<li>D7(“13.8”)</li>
<li>D8(“13,8”)</li>
<li>D9(“13.8h”)</li>
<li>D10(“13,8h”)</li>
<li>D11(“13:48”)</li>
<li>D12(“13h 48m”)</li>
</ul>
<p><strong>The following formats use calendar work time settings</strong></p>
<ul>
<li>D13(“10d”)</li>
<li>
<p>D14(“10 days”)</p>
</li>
<li>D15(“10d 15h”)</li>
<li>
<p>D16(“10 days 15 hours”)</p>
</li>
<li>D18(“8w”)</li>
<li>
<p>D19(“8 weeks”)</p>
</li>
<li>D20(“8w 6d”)</li>
<li>
<p>D21(“8 weeks 6 days”)</p>
</li>
<li>D23(“8w 6d 13h”)</li>
<li>
<p>D24(“8 weeks 6 days 13 hours”)</p>
</li>
<li>D26(“2m 3w”)</li>
<li>
<p>D27(“2 month 3 weeks”)</p>
</li>
<li>D29(“2m 3w 6d”)</li>
<li>
<p>D30(“2 month 3 weeks 6 days”)</p>
</li>
<li>D32(“1y 2m 3w”)</li>
<li>
<p>D33(“1 year 2 month 3 weeks”)</p>
</li>
<li>D35(“1y 2m 3w 6d”)</li>
<li>
<p>D36(“1 year 2 month 3 weeks 6 days”)</p>
</li>
<li>D38(“1y 2m 3w 6d 13h”)</li>
<li>
<p>D39(“1 year 2 month 3 weeks 6 days 13 hours”)</p>
</li>
<li>D41(“1y 2m 3w 6d 13h 5m”)</li>
<li>D42(“1 year 2 month 3 weeks 6 days 13 hours 5 minutes”)</li>
</ul>
<p>D13 and higher formats use <em>Work time settings</em> calendar settings.
These settings specify the length of the working day/week/month/year in seconds for your work schedule.
Soon we will add an automatic calculation of the average duration of these values, depending on the specified schedule.</p>
<p style="text-align: center;"><a href="/uploads/time-in-status/work-calendar/time-settings.png"><img src="/uploads/time-in-status/work-calendar/time-settings.png" style="width:50%" /></a></p>JiBrokWe have added support for new formats for displaying time. Now you can display time converted to minutes/hours/days/weeks/months/years.Time statistic (Time in status Cloud)2021-10-14T00:00:00+00:002021-10-14T00:00:00+00:00https://jibrok.com/Time%20statistic(Time%20in%20status%20Cloud)<p>In the new version, we have added a number of functions for calculating various statistics.</p>
<h2 id="general-information">General information</h2>
<ul>
<li>Functional for working with statistics is able to count average values, highs, lows and percentiles.</li>
<li>You can display the calculation of statistics in fields, web panels or dashboards.</li>
<li>You can use JQL search to work with statistical data.</li>
</ul>
<h3 id="more-details">More details</h3>
<h4 id="fields">Fields</h4>
<ul>
<li>In the field settings, you can configure how the statistical functions are counted. Tasks are configured (how much and for what period to take) that will be used to calculate statistics.</li>
</ul>
<p style="text-align: center;"><a href="/uploads/tis-cloud/field-statistic-settings.png"><img src="/uploads/tis-cloud/field-statistic-settings.png" style="width:100%;" /></a></p>
<ul>
<li>Field statistics are calculated for each context separately.</li>
<li>Functions will always be calculated and will be available to work in JQL(The data is updated at least once a day.).</li>
<li>You can also add a single function display to a field.</li>
</ul>
<p style="text-align: center;"><a href="/uploads/tis-cloud/display-settings.png"><img src="/uploads/tis-cloud/display-settings.png" style="width:100%;" /></a></p>
<p style="text-align: center;"><a href="/uploads/tis-cloud/field-view-average-time-example.png"><img src="/uploads/tis-cloud/field-view-average-time-example.png" style="width:100%;" /></a></p>
<ul>
<li>Statistics are calculated separately from the base value. Therefore, changing field settings will not immediately reflect updated statistics.</li>
</ul>
<h4 id="jql">JQL</h4>
<ul>
<li>On the start page, we have added examples of JQL queries for working with statistics. Functions work according to the logic of comparing the time value in the task with the value of the specified function. (Each function value is calculated for each context separately)</li>
</ul>
<p style="text-align: center;"><a href="/uploads/tis-cloud/jql-statistic-examples.png"><img src="/uploads/tis-cloud/jql-statistic-examples.png" style="width:100%;" /></a></p>
<h4 id="web-panels">Web Panels</h4>
<ul>
<li>For panels, issues for calculating statistics are set up according to a similar scheme (as for fields).</li>
</ul>
<p style="text-align: center;"><a href="/uploads/tis-cloud/web-panel-statistic-settings.png"><img src="/uploads/tis-cloud/web-panel-statistic-settings.png" style="width:100%;" /></a></p>
<p>View example:</p>
<p style="text-align: center;"><a href="/uploads/tis-cloud/web-panel-statistic-demo.png"><img src="/uploads/tis-cloud/web-panel-statistic-demo.png" /></a></p>
<ul>
<li>Statistics are calculated as a whole for each panel separately (for all specified projects and request types together). We will do the division in the near future so that the data in the panel can be calculated separately for each project/issue type.</li>
</ul>
<h4 id="dashboard-gadget">Dashboard gadget</h4>
<ul>
<li>We have also prepared a gadget for the desktop. It allows you to calculate any statistics for any request. He is as flexible as possible.</li>
</ul>
<p style="text-align: center;"><a href="/uploads/tis-cloud/dashboard-gadget-calculate-statistic-add-and-settings.png"><img src="/uploads/tis-cloud/dashboard-gadget-calculate-statistic-add-and-settings.png" style="width:100%;" /></a></p>
<p>View Example:</p>
<p style="text-align: center;"><a href="/uploads/tis-cloud/dashboard-gadget-calculate-statistic-example.png"><img src="/uploads/tis-cloud/dashboard-gadget-calculate-statistic-example.png" style="width:100%;" /></a></p>
<ul>
<li>This is a small report in which two columns are configured. The first is the heading, the second is the value calculated in accordance with the settings.</li>
<li>You can add an unlimited number of lines.</li>
<li>For each line, queries are indicated on the basis of which it is necessary to calculate the value of the function and the function itself. You can specify arbitrary statuses and Jql query, or select one of the contexts of existing fields.</li>
<li>The gadget is still in Beta version and does not support “personal appeal” - requests like assignee = currentUser () do not work, but you can specify a specific user.</li>
</ul>JiBrokIn the new version, we have added a number of functions for calculating various statistics. General information Functional for working with statistics is able to count average values, highs, lows and percentiles. You can display the calculation of statistics in fields, web panels or dashboards. You can use JQL search to work with statistical data.⭐️ Fields panel for Jira Service Management - Public release ⭐️2021-10-12T00:00:00+00:002021-10-12T00:00:00+00:00https://jibrok.com/Fields%20panel%20for%20Jira%20Service%20Management%20-%20Public%20resease<p>View app on <a href="https://marketplace.atlassian.com/apps/1226586/fields-panel-for-jira-service-management-jsm?tab=overview">Atlassian Marketplace</a></p>
<h2 id="welcome-to-fields-panel-for-jira-service-management-jsm">Welcome to Fields panel for Jira Service Management (JSM)!</h2>
<p>This is a application that allows you to display any issue fields to customers of the Jira Service Management portal.</p>
<p>For customization, two panels are provided with different placement on the portal(view request screen).</p>
<p style="text-align: center;"><a href="/uploads/jsm-fields-panel-cloud/two-panels-example.png"><img src="/uploads/jsm-fields-panel-cloud/two-panels-example.png" style="width:100%" /></a></p>
<p>On each panel, you can display any number of fields and optionally the name and description of the panel. Description can contain plain or HTML text. This allows you to use the panels, including for displaying messages on the portal.</p>
<p>Panels only shown in created requests. They cannot be displayed on the request creation screens.</p>
<h3 id="panel-settings">Panel settings</h3>
<p>After installing the application, go to the project settings (project type: Service Management) and open the new menu <strong>Fields panels for customer</strong>:</p>
<p style="text-align: center;"><a href="/uploads/jsm-fields-panel-cloud/open-settings.png"><img src="/uploads/jsm-fields-panel-cloud/open-settings.png" style="width:100%" /></a></p>
<p>An interface for customizing panels with fields will open. This interface is available to <strong>Project Administrator</strong>.</p>
<p>The first thing you need to do is create a panel. To do this, open the tab with “Fields panels”.</p>
<p style="text-align: center;"><a href="/uploads/jsm-fields-panel-cloud/open-fields-panels.png"><img src="/uploads/jsm-fields-panel-cloud/open-fields-panels.png" style="width:100%" /></a></p>
<p style="text-align: center;"><a href="/uploads/jsm-fields-panel-cloud/create-fields-panel.png"><img src="/uploads/jsm-fields-panel-cloud/create-fields-panel.png" style="width:100%" /></a></p>
<ul>
<li>Click the <strong>create</strong> button.</li>
</ul>
<p style="text-align: center;"><a href="/uploads/jsm-fields-panel-cloud/settings-of-fields-panel.png"><img src="/uploads/jsm-fields-panel-cloud/settings-of-fields-panel.png" style="width:100%" /></a></p>
<ul>
<li>Name - it can be technical (if it will not be displayed on the portal) or carry some kind of information to the user (if you want to display it on the portal).</li>
<li>Description - can be left blank, filled with technical information or some kind of message for the user. You can specify the HTML that will be displayed on the portal.
<ul>
<li>Preview description as HTML - will show how the description will look on the portal.</li>
</ul>
</li>
<li>Specify the fields that you want to display in this panel. <em>If the field is displayed incorrectly on the portal, please write to support, we will quickly add it. This applies primarily to fields from third-party applications.</em></li>
<li>Specify whether to display the name and description on the portal.</li>
<li>Click the <strong>save</strong> button.</li>
</ul>
<p>Go to the first tab <strong>Mapping request types and field panels</strong>.</p>
<p>Now you can set for what type of request and where to display this panel.</p>
<ul>
<li>To do this, click on the <strong>edit</strong> button opposite the required type of request.</li>
</ul>
<p style="text-align: center;"><a href="/uploads/jsm-fields-panel-cloud/open-settings-of-request-type.png"><img src="/uploads/jsm-fields-panel-cloud/open-settings-of-request-type.png" style="width:100%" /></a></p>
<ul>
<li>In the menu that opens, select the panel to display at the top of the request and in the side.</li>
</ul>
<p style="text-align: center;"><a href="/uploads/jsm-fields-panel-cloud/settings-of-request-type.png"><img src="/uploads/jsm-fields-panel-cloud/settings-of-request-type.png" style="width:100%" /></a></p>
<ul>
<li>Click the <strong>save</strong> button.</li>
</ul>
<p>This completes the configuration and the selected fields are displayed on the portal.</p>
<p style="text-align: center;"><a href="/uploads/jsm-fields-panel-cloud/view-example.png"><img src="/uploads/jsm-fields-panel-cloud/view-example.png" style="width:100%" /></a></p>
<p>View app on <a href="https://marketplace.atlassian.com/apps/1226586/fields-panel-for-jira-service-management-jsm?tab=overview">Atlassian Marketplace</a></p>JiBrokView app on Atlassian Marketplace