New Bugs in software

[Wp]

1. The child issues of an epic used to sort by key, now they are sorting randomly.
   1. Relates to: https://community.atlassian.com/t5/Jira-Software-questions/Epic-Child-Tasks-Sorted-Randomly-At-Worst-or-Arbitrarily-in-the/qaq-p/2588254
2. It appears that now, randomly, some kind of Jira automation (that I confirmed we did not setup) is automatically adding issues as related, even if they are already linked as blockers or children tasks
   1. relates to the following, providing this is wrong from a project management perspective. https://community.atlassian.com/t5/Jira-Software-questions/quot-child-issues-quot-and-quot-linked-issues-quot-are/qaq-p/2539074
   2. This is starting to cause complete and total havoc on our tickets. 'relates' is the least useful link type and has zero value if used in this regard. Only blockers have true value as a link type to projects process... the rest are considered ;info only'.
   3. i.e. please turn off this automation, it only started last night. Someone said it appears to automatically link as related if you mention an issue in a comment... even if its already linked as a blocker or epic child.

[Trudy Claspill]

Hello @Wp 

1. The sort order is not random. You can elect how you want them sorted by clicking on the Order By option above the Child Issues list. If you don't select anything then they are sorted by Rank.

2. Do you see the creation of the links noted in the Issue History? Have you confirmed with whomever the action is attributed to that they did not, in fact, directly create the issue link? Has a Jira Administrator reviewed the Audit Logs for Automation Rules at a global level to see if there is an automation rule running at the same time?

2.1. The author of that post responded that they did find an automation was causing the link to be created. 

2.3 Atlassian has not imposed any automation rules into your instance that are causing a link to be created between an issue and other issues mentioned in Comments. If that is indeed occurring, then that Automation Rule was created by some user or administrator of your instance, and your Jira Administrators have the access needed to find that rule and disable it.

[Wp]

1. Terrible programming: if the default sort order is rank: (1) why is rank not even listed as an option (2) why isn't the dropdown defaulting its value to rank. (3) why isn't the rank (number I presume) listed with each row (4) why is it impossible to set rank from the list view herein and the ticket itself... I plan epics, not sprints that is someone else's job, so any type of board view your suggestion would require 1 board per epic which is insaine. Can you please escalate the multiple tickets requesting that this interface be repaired for standard functionality...
   • FYI - the reason the sort feature was implemented herein, is that there was a ticket requesting the ability to manually sort child issues in epics in the same way we can subtasks in stories, and for an unknown reason you designed to implement sort for epic children instead and not for subtasks in stories, creating an insane asymmetry in things that are inherently symmetrical in nature  (no one on any team I have been on has ever knowing used the rank field... make it more obvious so these bug request resolutions become more obvious). Proof: 
     • JRACLOUD-76877
     • JRACLOUD-40929
2. Isolated issue: See screenshots. I can confirm that anytime a user enters a comment with a ticket number in it, it gets added as related even if already added as a blocker.
   • Can you please confirm this is NOT default operation?
   • Assuming the previous is true, can you please tell me where I should tell the Admin to go to look to fix locate and repair the custom automation? turnover is high and the Admin is not necessarily a jira SME.

.

asdfasdf

[Trudy Claspill]

Hello @Wp 

1.1 and 1.2: I don't know. I am just another user of the products, like you. I have no special insights into the design decisions made by Atlassian.

1.3 Rank is not a number. It is an alphanumeric code used internally by the product to denote the relative rank of an issue compared to other issues. Ranking of issues is a global setting, not a board specific setting. Because the value cannot be easily interpreted or set by a person, there is no value in displaying it.

1.4

- I don't know why it isn't possible to drag and drop child issues within the Epic Details View to re-rank them. See my answer to 1.1/1.2.

- It is not able to be set within the individual issue for the reasons stated in 1.3.

And, no, I can't escalate the Jira issues because I am just another user of the product. Get all you Jira friends to Vote for the issues. The second one is already marked as Done. The first one is a Suggestion. Refer to Atlassian's New Feature Implementation policy for information on how they choose suggestions/features to implement.

2.1 I can confirm that what you are experiencing is not built in/default functionality of the Jira Software product.

2.2

The history screen image you provide is a clear indication that the link was added by Automation because it says the responsible party is Automation for Jira.

In either that issue or the other issue to which it is linked you should see a reference to the rule that was run.

Viewing the details of the issue look at the panels on the right. Below Details and More Fields is one labeled Automation. Expand that one and click the refresh button in it.

That will show you a list of rules run against that issue recently. The rule title can be clicked to go directly to the rule details, if you have sufficient permissions.

Additionally Jira Administrators can find the audit log for all rule execution activity by 

- clicking on the gear icon near their avatar

- selecting System

- in the new display, finding Global Automation in the panel on the left and clicking that

- clicking on the Audit Log tab

The page will display entries for every rule across the system for configuration changes and executions. They should look for entries that occur near the time the link was created. They can expand the entry to see what issues the rule executed against. They can follow the link to go directly to the rule to see the details of it. If your Jira Administrators are not well versed in Jira functionality (which is a mistake) then somebody who is and who knows about Automation Rules specifically should do a screen share with the administrators to review the information.

More information about Automation Rules can be found at:

https://support.atlassian.com/cloud-automation/docs/jira-cloud-automation/

More information specifically about debugging rules and links to info about the audit log can be found here:

https://support.atlassian.com/cloud-automation/docs/debug-an-automation-rule/

Your administrators can also open a support ticket directly with Atlassian to get additional assistance.