- Created by Seibert Media employee, last modified on Oct 10, 2017
No, both plugins work separately.
Nothing, Issue Manger doesn't affect Atlassian's Jira standard macro.
Basically yes, but the Issue Manager still has some technical dependencies on the Jira standard macro and won't work without it. Our goal is that Issue Manager will work completely autonomously, so the standard Jira macro of Atlassian can be deactivated.
Yes, as long as no SSO (Single Sign On) is configured.
The deletion of a Issue Manager macro doesn't have any effects on the corresponding Jira issue. To delete a Jira issue go to Jira.
Issue Manager displays the following:
Yes, as long as those fields are not required fields.
Issue Manager supports currently more than 50% of all Jira field types. Our goal is that Issue Manager will support all standard field types in the near future. Keep in mind that it's still possible to create issues with Issue Manager if there are unsupported fields within the form as long as they aren't required fields.
Supported field types | Field types that are supported with limitations | Field types that are not supported |
---|---|---|
|
|
|
Currently not. If you are interested in such features, please contact us for a sponsored development.
- via e-mail: jira-support@seibert-media.net
- Fill out the contact form below and we will get back to you quickly.
Open the full search of Confluence and type in the following query into the search field:
macroName:conjira-issue
Diese Seite auf Deutsch ansehen.
- No labels
This content was last updated on 10/10/2017.
This content hasn't been updated in a while. That doesn't have to be a problem. Some of our pages live for years without becoming obsolete. Please click this link if you want us to update this page. Old content can be incorrect, misleading or outdated. Please get in contact with us via a form on this page, our live chat or via email with content@seibert.group if you are in doubt, have a question, suggestion, or want changes from us.