Jira Description Markdown

broken image


  1. Even if using the same custom field configuration scheme among multiple projects, you can still visit an individual custom field in the Custom Field configuration page and add a custom field.
  2. Python JIRA.projectcomponents - 5 examples found. These are the top rated real world Python examples of jira.JIRA.projectcomponents extracted from open source projects. You can rate examples to.
Description

This blog is about how to manage issue types, sprints and backlogs in Jira. This blog is the 2nd part in the series on the use of Jira issue types. One specific issue is that when using the Markdown from URL with a Github URL, the code blocks that come from github don't get displayed in.

  • Status:Applied(View Workflow)
  • Resolution: Persuasive
  • Specification:
  • Raised in Version:
  • Work Group:
  • Related Artifact(s):
  • Resolution Description:
  • Resolution Vote:
  • Change Category:
  • Change Impact:
  • Pre Applied:

This proposal is to add Ingredient.description, so that it is possible to have an uncoded (textual) list of ingredients, or of excipients, and still to be tell these categories apart using Ingredient.role (active vs excipient etc).

Some systems have coded/structured lists of ingredients but only a textual list of excipients (in one long text string).

An uncoded single ingredient can go in Ingredient.Substance.code.text, but there is nowhere currently for a list of multiple or for some general text about the ingredient(s).

Update 31st March:

In keeping with other description fields this should be Markdown rather than a plain string

Watchers:
1Start watching this issue

This authentication modules lets users log in to Hub with their Jira accounts.

Enable Jira Authentication

Jira Description Template

To allow users to sign in to Hub with their Jira accounts, enable a Jira authentication module.

To enable the module, follow these steps.

To enable Jira authentication:

Description

Requires permissions: Low-level Admin Write

Jira Description Markdown
  1. In the Access Management section of the Administration menu, select Auth Modules.

  2. From the Add Module drop-down list, select Atlassian Jira.

    • The Add Module dialog opens.

  3. In the Add Module dialog, enter values for the following settings:

    FieldDescription
    NameEnter a name for the authentication module.
    Server URLEnter the server address of the Jira instance. For example, http://mycompany.com/jira.
    • The Jira authentication module is created, enabled, and configured automatically.

    • The Auth Modules page displays the settings for the Jira authentication module. For additional information about the settings on this page, see the Settings section.

    • Users can log in to Hub with their Jira credentials.

Test the Connection

To verify that the authentication module is connected to your Jira instance, test the connection.

Use

This blog is about how to manage issue types, sprints and backlogs in Jira. This blog is the 2nd part in the series on the use of Jira issue types. One specific issue is that when using the Markdown from URL with a Github URL, the code blocks that come from github don't get displayed in.

  • Status:Applied(View Workflow)
  • Resolution: Persuasive
  • Specification:
  • Raised in Version:
  • Work Group:
  • Related Artifact(s):
  • Resolution Description:
  • Resolution Vote:
  • Change Category:
  • Change Impact:
  • Pre Applied:

This proposal is to add Ingredient.description, so that it is possible to have an uncoded (textual) list of ingredients, or of excipients, and still to be tell these categories apart using Ingredient.role (active vs excipient etc).

Some systems have coded/structured lists of ingredients but only a textual list of excipients (in one long text string).

An uncoded single ingredient can go in Ingredient.Substance.code.text, but there is nowhere currently for a list of multiple or for some general text about the ingredient(s).

Update 31st March:

In keeping with other description fields this should be Markdown rather than a plain string

Watchers:
1Start watching this issue

This authentication modules lets users log in to Hub with their Jira accounts.

Enable Jira Authentication

Jira Description Template

To allow users to sign in to Hub with their Jira accounts, enable a Jira authentication module.

To enable the module, follow these steps.

To enable Jira authentication:

Requires permissions: Low-level Admin Write

  1. In the Access Management section of the Administration menu, select Auth Modules.

  2. From the Add Module drop-down list, select Atlassian Jira.

    • The Add Module dialog opens.

  3. In the Add Module dialog, enter values for the following settings:

    FieldDescription
    NameEnter a name for the authentication module.
    Server URLEnter the server address of the Jira instance. For example, http://mycompany.com/jira.
    • The Jira authentication module is created, enabled, and configured automatically.

    • The Auth Modules page displays the settings for the Jira authentication module. For additional information about the settings on this page, see the Settings section.

    • Users can log in to Hub with their Jira credentials.

Test the Connection

To verify that the authentication module is connected to your Jira instance, test the connection.

  1. Click the Test Login button.

  2. In the Test Authentication dialog, enter the credentials of a user who is stored in your Jira instance:

    • In the Username field, enter the domainusername.

    • In the Password field, enter the password.

  3. Click the Test Login button.

    • Hub searches for the specified user account in the Jira instance. If the user is found, a success notification is displayed. If you get an error, check your user credentials and server URL.

Settings

The settings are configured automatically when the module is added to Hub. You do not have to change these settings. To configure the options that define how Hub treats new user accounts with Jira credentials, see Additional Settings.

FieldDescription
TypeDisplays the name of the application or service that is enabled for third-party authentication in Hub.
NameStores the name of the authentication module. Use this setting to distinguish this module from other authentication modules in the Auth Modules list. The name is also shown in the tooltip for the third-party service icon on the login form.
Server URLStores the URL used to authenticate a login request in Hub.
Change Password URIStores the URL of the page used to manage change password requests for a Jira account.
SSL keySelects an SSL key that can be used to verify the identity of your YouTrack installation to Jira. You should only need to use this setting when your Jira installation requires client SSL authentication. For more information about managing SSL keys in YouTrack, see SSL Keys.

Additional Settings

These settings let you manage Hub account creation and group membership, and to reduce the loss of processing resources consumed by idle connections.

Jira Description Field

OptionDescription
User creationEnables creation of Hub accounts for unregistered users who log in with an account that is stored in the connected authorization service. Hub uses the email address to determine whether the user has an existing account.
Auto-join groupsAdds users to a group when they log in with an account that is stored in the connected authorization service. You can select one or more groups. New users that auto-join a group inherit all of the permissions assigned to this group.
We recommend that you add users to at least one group. Otherwise, a new user is only granted the permissions that are currently assigned to the All Users group.
Connection timeoutSets the period of time to wait to establish a connection to the authorization service. The default setting is 5000 milliseconds (5 seconds).
Read timeoutSets the period of time to wait to read and retrieve user profile data from the authorization service. The default setting is 5000 milliseconds (5 seconds).
AuditLinks to the Audit Events page in Hub. There, you can view a list of changes that were applied to this authentication module.




broken image