...
| Tip | ||
|---|---|---|
| ||
We've increased the prices of Requirement Yogi in 2.0.0, but we offer our current customers to remain on the old price. Please ask us for a voucher until 30/05/2020 if you've first purchased Requirement Yogi before 30/05/2019. |
| Warning | ||
|---|---|---|
| ||
We are going to publish a Data Center edition of Requirement Yogi. We are required to notify customers because it will impact their pricing if they renew their license. |
| Info | ||
|---|---|---|
| ||
Please read the first paragraph of this page: You must provide an administrator login in the Requirement Yogi configuration, for the connection between Confluence and Jira. |
Important: Please set the administrator credentials
...
What are those credentials for?
...
Modifications in Jira will be performed under this username, not under the name of the person who performed the change.Status colour Yellow title Author is lost
Soon Next month, if you upgrade the Jira side to RY a version 2.2.3x that we'll publish for Jira, then Jira will display the real author of the changes in the history panel (as displayed in Confluence at the time of editing), instead of this username.Status colour Yellow title In a near future
Should I be worried that my login is being used here?
- No. It also fixes the a bug where changes would sometimes be attributed to a wrong user anyway. At least, in our situation, changes are always attributed to the user that is specified; and in a near future, Requirement Yogi in Jira will display the Confluence user who performed the changes.
- It is limited to only change the RIL ("Remote issue links") in Jira, and only those of type "Requirement Yogi".
- You're not giving "us" any information by providing your login here. If we just wanted some login, we could get it from the database.
...