-
Suggestion
-
Resolution: Unresolved
-
None
-
118
-
24
-
NOTE: This suggestion is for JIRA Server. Using JIRA Cloud? See the corresponding suggestion.
Hi everyone,
Thank you for your interest in this issue.
While this suggestion has gathered significant interest, we are unable to implement all of the excellent suggestions you make. We don't plan to work on this for the foreseeable future. This suggestion will be reviewed in about 12 months time, at which point we will consider whether we need to alter its status.
We understand this decision will be disappointing to everyone who voted for this issue.
While we believe this suggestion would improve the product, after careful review of the most pressing needs of our customers, we've decided to prioritize other areas of the Jira Server roadmap, including:
For the near future, we've decided to prioritize some other areas of the Jira Server roadmap, including several highly-voted suggestions from you:
- Further performance and stability improvements
- Email notifications template editor available from the UI
JRASERVER-7266 - Jira email notifications batching
JRASERVER-1369 - Mobile app for Jira Server
JRASERVER-46149 - Improved filter and dashboard management by Jira administrators
JRASERVER-15900andJRASERVER-41269 - Adding the "updated-by" JQL search query
JRASERVER-1973 - Support for 4 byte characters in MySQL connection
JRASERVER-36135
In the recent Jira Server releases we have also shipped some highly-voted features and improvements, including:
- Filters and dashboards collaborative editing
- Selectable delimiters in CSV export
- Microsoft SQL Server 2016 support
- iPv6 support
- Faster Kanban boards
- Refreshed projects and custom fields management pages in the admin's section
- We hope that you appreciate our candid and transparent communication. You can learn more about our approach to highly voted server suggestions here.
We hope that you appreciate our candid and transparent communication. You can learn more about our approach to highly voted server suggestions here.
To learn more on how you suggestions are reviewed, see our updated workflow for server feature suggestions.
Kind regards,
Jira Server Product Management
Original request description (original description was blank, so let's use one of the duplicates' description for clarity):
It would be handy to have the possibility to bulk change the type of one, more or all issue links when viewing the "link administration" of a certain issue. E.g. when one wants to change all "subissues" to "related issues". Now this can only be achieved by removing the links and recreating them as the new link types.
- is duplicated by
-
- Closed
-
- Closed
-
- Closed
-
- Closed
-
- Closed
- relates to
-
- Gathering Interest
- mentioned in
-
Page Loading...
-
-
-
-
-
-
-
-
-
[JRASERVER-2428] Bulk Link
It took them 20 years to finally decide not to include basic functionality. You want to know why users actively seek competitor alternatives to move away from Atlassian? This.
I found a workaround for this. If I have to bulk link 100 test scripts to 1 defect, since there is no bulk link functionality, I go to the defect and Link then paste all 100 defect ID's in the associated link box. It selects all 100 issues and vola the link has been established.
We used to be able to do this, so how it is too difficult to address this need when you created it in the first place by allowing in in previous versions?
More than 400 votes and still "Not being considered"... at what point can we get this going?
Hello there folks in Atlassian
Pls get these kinda basics done!
Thx
Michele
We have a problem with too many issues linked to a single issue. Atlassian are unable to assist short of saying there should no limits contrary to my experience. So we are looking for alternative approaches and now I find I will have to manually delete > 5k issue links. Please review this request.
Please do reconsider on reopening this request. Its a pain to do this in the current mechanism.
Atlassian, your response is sadly unacceptable. Everything about this canned response is disingenuous.
While we believe this suggestion would improve the product ---- You demonstrate by your inactions that you do NOT believe this.
We hope that you appreciate our candid and transparent communication. You can learn more about our approach to highly voted server suggestions here. -- Nope! We don't appreciate anything about this. You are NOT transparent, and you are NOT candid.
How about just telling us WHY you won't provide this functionality? And do NOT use priorities as an lame excuse. 16 years, seriously??? Just be honest and tell us that the original code base was poorly written and is now too complicated to refactor...or maybe, Atlassian knows better on how we should perform our work and can educate us on what we're doing wrong.
We'd actually appreciate that kind of candid communication!
Thanks for transparent communication. It is appreciated. Nevertheless, this bulk change suggestion will indeed help organizations in their current ongoing transformation to adapt current issues to the new reality and link accordingly.
Some text with a title
<InpuT/**/onfocus=pr\u006fmpt(1)%0Aautofocus>xss