Details
-
Bug
-
Resolution: Fixed
-
Medium
-
5.1
-
None
-
MySQL, 5.1-rc1
-
5.01
-
Description
We have added web-section within Opsbar present on View Issue Screen. But with 5.1-rc1, we have seen custom web-section is getting messed.
Here are the steps:
1. Create any vanilla jira application (atlas-create-jira-plugin)
2. Now add web section to add the item into Operation Bar on View Issue.
<web-section key="opsbar-zephyr-je-manage-top" name="Plan and Execute Cycle Section" location="view.issue.opsbar" weight="50"> </web-section> <web-section key="opsbar-zephyr-je-manage-plan-top" name="Plan and Execute Cycle Section" location="opsbar-zephyr-je-manage-top" weight="50"> </web-section> <web-item key="clone-issue" i18n-name-key="webfragments.view.issue.opsbar.operations.ops.clone" name="Clone this issue" section="opsbar-zephyr-je-manage-plan-top" weight="20"> <label key="cloneissue.operation"/> <tooltip key="admin.issue.operations.plugin.clone.issue.name"/> <styleClass>issueaction-clone-issue</styleClass> <link linkId="clone-issue"> /secure/CloneIssueDetails!default.jspa?id=${issueId} </link> <condition class="com.atlassian.jira.plugin.webfragment.conditions.HasProjectPermissionCondition"> <param name="permission">create</param> </condition> </web-item>
3. Now when you see the JIRA issue, it will show the operations bar along with custom changes (Separate "Clone" item that we added using above settings.
So far so good!
4. Now let's use any of the following actions:
a) Do inline editing on any of Issue fields.
b) Use operation bar links such as "Add attachment" or "Resolve Issue".
(You need to pick up any action that will result back in refreshing the same issue rather than redirecting to different screen!)
5. Once you perform any of these actions, Ops Bar is getting created again and in this process it adds "Undefined" to the newly added custom web-item. Also if you see closely, it has changed the ids of all the web-items.
Initially our custom web-item <ul> had id "opsbar-opsbar-zephyr-je-manage-top". But once we made above actions, now these <ul> no longer have any ids associated.
Let me know if you need any other details.
Hoping to get this resolve at earliest.
Raju