Wikipedia:Articles for deletion/Jira (software)


 * The following discussion is an archived debate of the proposed deletion of the article below. Please do not modify it. Subsequent comments should be made on the appropriate discussion page (such as the article's talk page or in a deletion review).  No further edits should be made to this page.

The result was keep. (non-admin closure) Mdaniels5757 (talk) 23:34, 11 July 2020 (UTC)

Jira (software)

 * – ( View AfD View log  Stats )

Atlassian as one article more than sufficient to cover all of their products. the company has made Wiki pages as some corporate blog for each of their products. Wiki is not a brochure. references are mainly their own and it is motivated by their PR/ digital marketing agency itself. and their articles were questioned for being written by close association of the company. Light2021 (talk) 07:10, 3 July 2020 (UTC)
 * Note: This discussion has been included in the list of Software-related deletion discussions. Shellwood (talk) 07:11, 3 July 2020 (UTC)


 * Keep This is technically a second nomination as the first was at Wikipedia:Articles for deletion/JIRA. A rewrite is still in order to remove promotional material, but it's quite notable. Multiple articles https://techcrunch.com/2020/01/23/jira-software-gets-better-roadmaps/ https://www.infoworld.com/article/3535008/5-apps-to-integrate-with-jira-software.html https://www.clariontech.com/platform-blog/jira-software-15-important-features-you-might-have-missed https://project-management.com/jira-software-review/ https://www.softwarepundit.com/jira-software-review https://oit.colorado.edu/services/business-services/jira-software LinkedIn Learning even has a number of courses on it: https://www.linkedin.com/learning/topics/jira . Multiple books on the topic: ISBN 1788833511 ISBN 978-1449305413  , and I did not scratch the surface there. I am assuming that Light2021 ignored the advice at WP:BEFORE and just went on the current state of the article. Walter Görlitz (talk) 07:59, 3 July 2020 (UTC)
 * Keep The topic is notable and so should be kept per WP:ATD; WP:IMPERFECT; WP:PRESERVE; &c. Andrew🐉(talk) 08:57, 3 July 2020 (UTC)

Keep per the significant coverage in multiple independent reliable sources.      </li> <li></li> <li></li> <li></li> <li></li> <li></li> </ol>

<ol> <li></li> <li></li> <li></li> <li> The abstract notes: "This paper describes an industrial case study using Atlassian JIRA® and third party plugins for requirements management in the field of transit systems. The solution presented shows efficiency in supporting the management of requirements, traceability and the systems engineering processes globally." The article notes: "Emerging from the software industry, Atlassian JIRA is a generic work item tracker (“work items” which JIRA calls “issues”) which is widely used for tracking software bugs and tasks and is also commonly used for Agile projects. JIRA has nonetheless a high level of configurability, which allow administrators to create legitimately all types of work items. Consequently, created work items can be requirement objects of all kinds (e.g. System Requirements, Software Requirements, or simply Requirements). All work items have a predefined set of data fields (properties or attributes), which are common to all tracked items, such as status, priority, version, etc. These properties are also configurable, and can be altered or complemented with new custom fields which can be specifically dedicated to requirements. For instance, we may want to characterize requirements with a Requirement Type, a Mode of Operation, a Source, a development Phase, a Component, a SubSystem, and so on. ... One big advantage of JIRA consists in that the tracking of a requirement can be closely coupled with the tracking of everything else related to it: sub-requirements, tasks, change requests, tests, bugs, project management items, and so on. This can be very helpful to SME, the number of resources being limited. It can also be applied to lean systems engineering concepts as described in [8] [9] and practices or even Agile systems engineering [10] where the need for delivering something quickly is a live or die factor. JIRA offers the ability to link items together. JIRA links go along with a link clause that describes the relationship between two linked items. The link clause is also configurable, and we may then correctly link requirements with, for instance, an “implements”-“implemented by” relationship. For instance, a Software Requirement may be implemented by a “Software Task” or by a “User Story” (for Agile fans). These links are the keys that enable traceability between objects (requirement to requirement, but also requirement to task, source code, test, change request, and so on)."</li> <li> The article notes: "JIRA is an issue tracking system developed by Atlassian Corporation starting in 2002. It is most commonly used for software bug tracking, but thanks to its advanced customization features, is highly suitable for other types of ticketing systems (work orders, help desks, etc.), and project management. ... JIRA provides a mature, powerful toolset for local customizations to meet specific project needs. This includes custom fields, issue types, workflows, notifications, and user entry screens. ... All software changes require a JIRA issue. This includes not just bug fixes, but enhancements and new features. In fact, documentation in JIRA issues is used as a basis for all end-user release documentation. In addition, database changes (in particular configuration data), code reviews, and design reviews are tracked with JIRA."</li> <li> The article notes: "The primary customer-facing UI for Jira Service Desk is its customer portal, but customers can also submit requests by using email and embedded widgets. When a request has been handled, an email will automatically be sent notifying the customer of its status. A link in the email will open the request in Jira Service Desk, with a full description of the status and any comments by the agent. A downside here compared to most of the other products we tested is Jira Service Desk's lack of an integrated knowledge base. According to Atlassian, this will be rectified in the next company fiscal year. Agents can search issues looking for how to resolve a specific problem, but there isn't a similar mechanism for the typical user."</li> <li> The article notes: "Atlassian’s JIRA began life as a bug-tracking tool. Today, though, it has become an agile planning suite, “to plan, track, and release great software.” In many organizations it has become the primary map of software projects, the hub of all development, the infamous “source of truth.” It is a truism that the map is not the territory. Alas, this seems especially true of JIRA. Its genesis as a bug tracker, and its resulting use of “tickets” as its fundamental, defining unit, have made its maps especially difficult to follow. JIRA1 is all too often used in a way which makes it, inadvertently, an industry-wide “antipattern,” i.e. “a common response to a recurring problem that is usually ineffective and risks being highly counterproductive.” One thing that writing elegant software has in common with art: its crafters should remain cognizant of the overall macro vision of the project at the same time they are working on its smallest micro details. JIRA, alas, implicitly teaches everyone to ignore the larger vision while focusing on details. There is no whole. At best there is an “Epic” — but the whole point of an Epic is to be decomposed into smaller pieces to be worked on independently. JIRA encourages the disintegration of the macro vision."</li> <li> The article notes: "A new customer coming to the Jira website might be confused about exactly the right software for them, as Jira Service Desk isn’t the only helpdesk solution that Atlassian sells. It also has Jira Core and Jira Software, so let’s explain how these are different from Jira Service Desk. Jira Core is a basic project management tool, aimed at helping an organisation implement change in a way where everyone understands the critical path and their part in it. Jira Software is also a management tool, but this one is focused on software development and integrates the tools used in those processes with functionality to keep all the developers on a big project linked to other team members and their code."</li> <li> The article notes: "Australian software giant Atlassian is giving its flagship product — Jira — a complete makeover, with company co-founder and co-CEO Scott Farquhar saying the move is a major investment in driving the $30 billion company’s future growth. ... Jira, the engine of Atlassian’s success, is a project management tool that allows software developers to manage their workflows. The software is used by developers to build better solutions and has a growing fanbase around the world, with 50,000 using Jira. The success of Jira has propelled Atlassian to the highest echelon of homegrown technology players, with the Nasdaq-listed company’s founders — Mr Farquhar and Mike Cannon-Brookes — feted for their innovation and seen as major players in the Australian business landscape."</li> <li> The article notes: "Atlassian's JIRA project-tracking tool has long been a popular choice among software developers, but on Tuesday the company showed it wants to reach a broader market by releasing three new editions tailored for different audiences. While JIRA Software retains the developer focus, promising agile best practices as defaults and deep integration with development tools, the other two extend beyond that original reach, which to date has placed the tool at about 35,000 companies, according to Atlassian."</li> <li> The article notes: "Kindly old Atlassian is making cloud-based versions of Jira Software, Confluence, Jira Service Desk, and Jira Core free for teams of up to ten people. ... The inflicting of Jira on potentially more people comes as companies adjust to the realities of remote working. Brainstorming on whiteboards and walls festooned with multi-coloured post-it notes (depending on which flavour of agile methodology has been spoonfed to managers) are not so simple once social distancing is factored in or offices are closed."</li> </ol>

There is sufficient coverage in reliable sources to allow Jira to pass Notability, which requires "significant coverage in reliable sources that are independent of the subject". Cunard (talk) 11:05, 6 July 2020 (UTC)</li></ul>


 * Related AfDs of other Atlassian products: Articles for deletion/Bamboo (software) (2nd nomination) and Articles for deletion/Confluence (software) (3rd nomination). Cunard (talk) 11:05, 6 July 2020 (UTC)
 * Delete all the sources are either primary, only contain extremely trivial information, or otherwise don't meet the notability standards. Including the new ones listed in the AfD. --Adamant1 (talk) 22:10, 9 July 2020 (UTC)
 * There are multiple books about Jira published by O'Reilly Media and Pakt. The books have names like Practical JIRA Administration, JIRA Essentials - Third Edition, and Mastering JIRA. These books are all independent of the company and cover Jira in-depth. Cunard (talk) 09:34, 10 July 2020 (UTC)


 * Pinging Articles for deletion/JIRA participants:, , and . Cunard (talk) 09:34, 10 July 2020 (UTC)
 * Unfortunately, users involved in the original AfD didn't provide any sources at the time to back their keeps votes with. Hopefully they do this time. Since a good portion of the ones provided by Cunard and in the article, along with Cunard's quotes are are suspect and trivial. Otherwise, this will just go to another AfD in a few more years. It's better to just settle it now instead by finding some actually usable sources IMO. --Adamant1 (talk) 10:11, 10 July 2020 (UTC)
 * Unfortunately we don't vote in delation discussions. Secondly, your argument is about the sources in the article. You ignored all of the sources (books) that I provided and all those that Andrew provided. Now, why was I pinged? Walter Görlitz (talk) 17:18, 10 July 2020 (UTC)
 * Obviously. I use the "vote" because its simpler and saves everyone time in reading then it would be going on the long tangent it would take for a more in-depth "true" description of the process. Everyone who's opinions matter, of which for me at least yours isn't included in, gets what I mean anyway. On the sourcing, if by Andrew you mean Cunard, the problem with him/her is WP:THREE or whatever it is. Instead of just providing the three sources that it would only take to establish notability he/she canvasses us repeatedly a ton of them that are usually not usable and then expects us to sift through the garbage to find the ones that are. Which it isn't on us to do. Same goes for the quotes. We don't need 50 mediocre sources for this, Just three good ones. And he/she has repeatedly refused to just provide them in-stead of ref-bombing. Personally, I'm not going to spend my day sifting through his/her trash to find something usable. Its not our jobs. The ones I did look at weren't good though. Maybe the 49th would be, but likely not and I have better things to do with my time then waste it trying to find out. I'm everyone here, including you, would agree that "Finding sources" doesn't mean "do a 1/1 word for word recreation in the AfD of everything you find on Google." Especially when it comes to the quotes, but also with the sources. Adamant1 (talk) 17:40, 10 July 2020 (UTC)
 * BTW, I see who you were talking about with Andrew now. I usually just see the snake emoji and associate Andrew the user with that. Anyway, the few sources he provided that I looked at were blog posts. Which he should really know aren't acceptable for establishing notability. So, i'd say the same thing applies in his case as Cunards. Either take the time to provide good sources or don't expect us to sift through the trash to find the goods ones. --Adamant1 (talk) 19:00, 10 July 2020 (UTC)


 * Keep per the multiple independent reliable sources cited about by Walter Görlitz and Cunard above. As shown above, whole books are devoted to Jira, and as with the IEEE and PC Magazine articles above, there are independent reviews, too. The topic seems highly notable. Given abundant sources, any problems with promotional content can be addressed. A highly notable topic and WP:SURMOUNTABLE problems suggest keeping the article. -- 18:41, 10 July 2020 (UTC)
 * Keep: JIRA is well known, and is the subject of many books, including Practical JIRA Administration (O'Reilly Media, 2011) and JIRA 8 Essentials (Packt Publishing, 2019). I agree with Adamant1 that Cunard's posts are sometimes hard to sift through, but a little mindful searching on Google Books or Newspapers.com often turns up decent sources for notable topics. — Toughpigs (talk) 23:46, 10 July 2020 (UTC)


 * The above discussion is preserved as an archive of the debate. <b style="color:red">Please do not modify it.</b> Subsequent comments should be made on the appropriate discussion page (such as the article's talk page or in a deletion review). No further edits should be made to this page.