{"id":79684,"date":"2020-04-29T19:42:05","date_gmt":"2020-04-29T17:42:05","guid":{"rendered":"https:\/\/prohoster.info\/blog\/administrirovanie\/kak-vnedrit-atlassian-jira-confluence-v-korporaczii-tehnicheskie-voprosy"},"modified":"2021-01-02T13:04:34","modified_gmt":"2021-01-02T11:04:34","slug":"kak-vnedrit-atlassian-jira-confluence-v-korporaczii-tehnicheskie-voprosy","status":"publish","type":"post","link":"https:\/\/prohoster.info\/ro\/blog\/administrirovanie\/kak-vnedrit-atlassian-jira-confluence-v-korporaczii-tehnicheskie-voprosy","title":{"rendered":"Cum s\u0103 implementa\u021bi Atlassian Jira + Confluence \u00een corpora\u021bii. Probleme tehnice","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"<p>Planifica\u021bi implementarea software-ului Atlassian (Jira, Confluence)? Nu dori\u021bi s\u0103 face\u021bi gre\u0219eli grave \u00een proiectare, care vor trebui rezolvate \u00een ultimul moment?<\/p>\n<p><img decoding=\"async\" alt=\"Cum s\u0103 implementa\u021bi Atlassian Jira + Confluence \u00een corpora\u021bii. Probleme tehnice\" src=\"\/wp-content\/uploads\/2020\/04\/7a7e616a26222da213ee14dec565a6f2.png\" style=\"display:block;margin: 0 auto;\"><br \/>\nAtunci veniti aici \u2014 analiz\u0103m implementarea Atlassian Jira + Confluence \u00een corpora\u021bii, \u021bin\u00e2nd cont de diferitele aspecte tehnice.<noindex><a rel=\"nofollow\" name=\"habracut\"><\/a><\/noindex><br \/>\nBun\u0103, sunt Proprietarul produsului la RSHB \u0219i sunt responsabil pentru dezvoltarea Sistemului de Gestionare a Cicelui de Via\u021b\u0103 (SGCV), construit pe produsele software ale companiei Atlassian Jira \u0219i Confluence.<\/p>\n<p>\u00cen acest articol voi descrie aspectele tehnice ale construirii SGCV. Articolul va fi util tuturor celor care planific\u0103 implementarea sau se ocup\u0103 de dezvoltarea Atlassian Jira \u0219i Confluence \u00een medii corporative. Articolul nu necesit\u0103 cuno\u0219tin\u021be speciale \u0219i este destinat unui nivel de familiarizare ini\u021bial\u0103 cu produsele companiei Atlassian. Va fi util administratorilor, proprietarilor de produs, liderilor de proiect, arhitec\u021bilor, tuturor celor care planific\u0103 implementarea sistemelor bazate pe software-ul Atlassian.<\/p>\n<h2>Introducere<\/h2>\n<p>Articolul va aborda \u00eentreb\u0103rile tehnice legate de implementarea Sistemului de Gestionare a Cicelui de Via\u021b\u0103 (SGCV) \u00een mediul corporativ. S\u0103 definim mai \u00eent\u00e2i ce \u00eenseamn\u0103 acest lucru.<\/p>\n<h4>Ce \u00eenseamn\u0103 o solu\u021bie corporativ\u0103?<\/h4>\n<p>\u00censeamn\u0103 o solu\u021bie:<\/p>\n<ol>\n<li><b>Scalabil\u0103.<\/b> \u00cen cazul cre\u0219terii \u00eenc\u0103rc\u0103rii, exist\u0103 posibilitatea tehnic\u0103 de a extinde puterea sistemului. Se disting scalarea orizontal\u0103 \u0219i vertical\u0103 \u2014 \u00een timpul scal\u0103rii verticale, puterea serverelor este crescut\u0103, iar \u00een scalarea orizontal\u0103, num\u0103rul serverelor pentru func\u021bionarea sistemului este crescut.<\/li>\n<li><b>Rezistent\u0103 la erori.<\/b> Sistemul va r\u0103m\u00e2ne disponibil \u00een cazul \u00een care un element iese din func\u021biune. \u00cen general, pentru sistemele corporative nu este necesar\u0103 rezisten\u021ba la erori, dar noi vom considera exact o astfel de solu\u021bie. \u00cen sistemul nostru sunt planifica\u021bi c\u00e2teva sute de utilizatori concuren\u021bi, iar timpii de nefunc\u021bionare vor fi foarte critici.<\/li>\n<li><b>Sus\u021binut\u0103.<\/b> Solu\u021bia trebuie s\u0103 se afle \u00een suport din partea furnizorului. Software-ul f\u0103r\u0103 suport trebuie \u00eenlocuit cu dezvolt\u0103ri proprii sau cu alt software cu suport.<\/li>\n<li>Instalare <b>Self-managed<\/b> (On-premise). Self-managed \u00eenseamn\u0103 posibilitatea de a instala software-ul nu \u00een cloud, ci pe servere proprii. Mai exact, aceasta include toate op\u021biunile de instalare care nu sunt SaaS. \u00cen acest articol, vom analiza op\u021biunile de instalare doar pentru Self-managed.<\/li>\n<li><b>Posibilitatea de dezvoltare \u0219i testare independent\u0103.<\/b> Pentru a organiza modific\u0103ri previzibile \u00een sistem, sunt necesare sisteme separate pentru dezvoltare (modific\u0103ri \u00een sistemul \u00een sine), sistem de testare (Staging) \u0219i sistem de produc\u021bie pentru utilizatori.<\/li>\n<li><b>Altele.<\/b> Suport\u0103 diverse scenarii de autentificare, suport\u0103 log-uri de audit, are un model de roluri configurabil etc.<\/li>\n<\/ol>\n<p>Acestea sunt elementele de baz\u0103 ale solu\u021biilor de afaceri \u0219i, din p\u0103cate, sunt adesea uitate \u00een timpul proiect\u0103rii sistemului.<\/p>\n<h4>Ce este un Sistem de Management al Ciclitului de Via\u021b\u0103 (SMCL)?<\/h4>\n<p>\u00cen termeni simplifica\u021bi, \u00een cazul nostru, acesta este Atlassian Jira \u0219i Atlassian Confluence \u2014 un sistem care ofer\u0103 instrumente pentru organizarea muncii \u00een echip\u0103. Sistemul nu 'impune' reguli de organizare a muncii, ci ofer\u0103 o varietate de instrumente pentru munc\u0103, inclusiv Scrum, tablouri Kanban, model de tip ap\u0103 c\u0103zut\u0103, Scrum scalabil etc.<br \/>\nDenumirea SMCL nu este un termen din industrie sau un concept de uz comun, ci este pur \u0219i simplu denumirea sistemului nostru \u00een Banc\u0103. SMCL pentru noi nu este un sistem de urm\u0103rire a erorilor, nu este un sistem de Management al Incidentelor \u0219i nici un sistem de Management al Modific\u0103rilor.<\/p>\n<h4>Ce implic\u0103 implementarea?<\/h4>\n<p>Implementarea solu\u021biei const\u0103 \u00eentr-o mul\u021bime de \u00eentreb\u0103ri tehnice \u0219i organiza\u021bionale:<\/p>\n<ul>\n<li>Alocarea capacit\u0103\u021bilor tehnice.<\/li>\n<li>Achizi\u021bionarea de software.<\/li>\n<li>Crearea echipei pentru implementarea solu\u021biei.<\/li>\n<li>Instalarea \u0219i configurarea solu\u021biei.<\/li>\n<li>Dezvoltarea arhitecturii solu\u021biei. Modelului de roluri.<\/li>\n<li>Dezvoltarea documenta\u021biei de operare, inclusiv instruc\u021biuni, reglement\u0103ri, proiect tehnic, proceduri etc.<\/li>\n<li>Schimbarea proceselor companiei.<\/li>\n<li>Crearea unei echipe de suport. Dezvoltarea SLA.<\/li>\n<li>Instruirea utilizatorilor.<\/li>\n<li>Altele.<\/li>\n<\/ul>\n<p>\u00cen acest articol, vom examina aspectele tehnice ale implement\u0103rii, f\u0103r\u0103 detalii privind componenta organiza\u021bional\u0103.<\/p>\n<h2>Particularit\u0103\u021bile Atlassian<\/h2>\n<p>Compania Atlassian este lider \u00een multe segmente:<\/p>\n<ul>\n<li><noindex><a rel=\"nofollow\" href=\"https:\/\/www.gartner.com\/doc\/reprints?id=1-6SEQV0Y&amp;ct=190607&amp;st=sb\">Gartner Magic Quadrant for Enterprise Agile Planning Tools<\/a><\/noindex><br \/>\n(Leadership-ul este determinat de achizi\u021bia reu\u0219it\u0103 a AgileCraft cu solu\u021bia sa cloud)<br \/>\n<img decoding=\"async\" alt=\"Cum s\u0103 implementa\u021bi Atlassian Jira + Confluence \u00een corpora\u021bii. Probleme tehnice\" src=\"\/wp-content\/uploads\/2020\/04\/68d9559051c2c3ea0891644612058fe2.png\" style=\"display:block;margin: 0 auto;\"><\/li>\n<li><noindex><a rel=\"nofollow\" href=\"https:\/\/thecantonsentinel.com\/technology\/10774\/application-lifecycle-management-tools-market-size-industry-status-and-growth-opportunities-for-leading-players-hp-atlassian-techexcel-ibm-microsoft-rocket-software\/\">Global Application Lifecycle Management Tools Market Share<\/a><\/noindex><img decoding=\"async\" alt=\"Cum s\u0103 implementa\u021bi Atlassian Jira + Confluence \u00een corpora\u021bii. Probleme tehnice\" src=\"\/wp-content\/uploads\/2020\/04\/50a4c5cebc3d5de61a95063004f5600d.png\" style=\"display:block;margin: 0 auto;\"><\/li>\n<\/ul>\n<p>Produsele companiei Atlassian dispun de toate func\u021biile necesare pentru mediul de afaceri. Voi men\u021biona urm\u0103toarele caracteristici:<\/p>\n<ol>\n<li>Solu\u021biile Atlassian se bazeaz\u0103 pe serverul web Java Tomcat. Software-ul Apache Tomcat vine inclus \u00een software-ul Atlassian, ca parte a instal\u0103rii; nu se poate schimba versiunea Apache Tomcat instalat\u0103 \u00eempreun\u0103 cu software-ul Atlassian, chiar dac\u0103 versiunea este \u00eenvechit\u0103 \u0219i con\u021bine vulnerabilit\u0103\u021bi. Singura op\u021biune este s\u0103 a\u0219tep\u021bi actualiz\u0103rile de la Atlassian, cu o versiune mai nou\u0103 de Apache Tomcat. De exemplu, \u00een versiunile actuale de Jira, se folose\u0219te Apache Tomcat 8.5.42, iar \u00een Confluence se folose\u0219te Apache Tomcat 9.0.33.<\/li>\n<li>Interfa\u021b\u0103 prietenoas\u0103, implementate cele mai bune practici disponibile pe pia\u021b\u0103 pentru aceast\u0103 clas\u0103 de software.<\/li>\n<li>Solu\u021bie complet personalizabil\u0103. Cu modific\u0103ri, se pot realiza orice ajust\u0103ri ale func\u021bionalit\u0103\u021bii de baz\u0103 pentru utilizator.<\/li>\n<li>Ecosistem dezvoltat. Exist\u0103 c\u00e2teva sute de parteneri: <noindex><a rel=\"nofollow\" href=\"https:\/\/partnerdirectory.atlassian.com\">https:\/\/partnerdirectory.atlassian.com<\/a><\/noindex>, inclusiv 16 parteneri \u00een Rusia. Anume prin parteneri \u00een Rusia se poate achizi\u021biona software-ul Atlassian, pluginuri, se poate urma training. Partenerii dezvolt\u0103 \u0219i \u00eentre\u021bin cea mai mare parte a pluginurilor.<\/li>\n<li>Magazine de aplica\u021bii (pluginuri): <noindex><a rel=\"nofollow\" href=\"https:\/\/marketplace.atlassian.com\">https:\/\/marketplace.atlassian.com<\/a><\/noindex>. Pluginurile extind semnificativ func\u021bionalitatea software-ului Atlassian. Func\u021bionalitatea de baz\u0103 a software-ului Atlassian este destul de modest\u0103, pentru aproape orice sarcin\u0103 apare necesitatea instal\u0103rii unor pluginuri suplimentare, fie gratuit, fie contra cost. Prin urmare, costurile pentru software ar putea fi semnificativ mai mari dec\u00e2t au fost estimate ini\u021bial.<br \/>\n\u00cen prezent, \u00een magazin sunt publicate c\u00e2teva mii de pluginuri, aproape o mie dintre acestea fiind testate \u0219i validate prin programul Data Center approved apps. Aceste pluginuri pot fi considerate stabile \u0219i potrivite pentru utilizare \u00een sisteme solicitate.<br \/>\nRecomand o abordare atent\u0103 \u00een ceea ce prive\u0219te planificarea pluginurilor, acest lucru influen\u021beaz\u0103 semnificativ costul solu\u021biei, multe dintre pluginuri pot duce la instabilitatea sistemului, iar produc\u0103torul pluginului poate s\u0103 nu ofere suport pentru rezolvarea problemelor.<\/li>\n<li>\u00censtruire \u0219i certific\u0103ri: <noindex><a rel=\"nofollow\" href=\"https:\/\/www.atlassian.com\/university\">https:\/\/www.atlassian.com\/university<\/a><\/noindex><\/li>\n<li>Sunt sus\u021binute mecanismele SSO, SAML 2.0.<\/li>\n<li>Suport pentru scalabilitate \u0219i redundan\u021b\u0103 exist\u0103 doar \u00een edi\u021biile Data Center. Aceast\u0103 edi\u021bie a ap\u0103rut pentru prima dat\u0103 \u00een 2014 (Jira 6.3). Func\u021bionalitatea edi\u021biilor Data Center este extins\u0103 \u0219i \u00eembun\u0103t\u0103\u021bit\u0103 constant (de exemplu, posibilitatea de instalare pe un singur nod a ap\u0103rut doar \u00een 2020). Abordarea pluginurilor pentru edi\u021biile Data Center s-a schimbat semnificativ \u00een 2018 cu introducerea aplica\u021biilor aprobate de Data Center.<\/li>\n<li>Costul suportului. Costul suportului din partea furnizorului este practic egal cu costul total al licen\u021belor software. Un exemplu de calcul al costului licen\u021belor este prezentat mai jos.<\/li>\n<li>Lipsa versiunilor Long Term. Exist\u0103 a\u0219a-numitele <noindex><a rel=\"nofollow\" href=\"https:\/\/confluence.atlassian.com\/enterprise\/atlassian-enterprise-releases-948227420.html\">versiuni Enterprise<\/a><\/noindex>, dar acestea, la fel ca toate celelalte versiuni, sunt suportate timp de 2 ani. Cu diferen\u021ba c\u0103 pentru versiunile Enterprise se elibereaz\u0103 doar corec\u021bii, f\u0103r\u0103 ad\u0103ug\u0103ri de noi func\u021bionalit\u0103\u021bi.<\/li>\n<li>Op\u021biuni extinse de suport (pentru un cost suplimentar). <noindex><a rel=\"nofollow\" href=\"https:\/\/www.atlassian.com\/enterprise\/support-services\">https:\/\/www.atlassian.com\/enterprise\/support-services<\/a><\/noindex><\/li>\n<li>Sunt suportate mai multe variante de SGBD. Software-ul Atlassian vine cu un SGBD gratuit H2, care nu este recomandat pentru utilizare \u00een produc\u021bie. Pentru utilizare \u00een produc\u021bie sunt suportate urm\u0103toarele SGBD-uri: Amazon Aurora (doar pentru Data Center) PostgreSQL, Azure SQL, MySQL, Oracle DB, PostgreSQL, MS SQL Server. Exist\u0103 restric\u021bii privind versiunile suportate \u0219i adesea doar versiunile mai vechi sunt acceptate, dar pentru fiecare SGBD exist\u0103 o versiune cu suport din partea furnizorului:<br \/>\n<noindex><a rel=\"nofollow\" href=\"https:\/\/confluence.atlassian.com\/adminjiraserver\/supported-platforms-938846830.html\">Platformele suportate de Jira<\/a><\/noindex>,<br \/>\n<noindex><a rel=\"nofollow\" href=\"https:\/\/confluence.atlassian.com\/doc\/supported-platforms-207488198.html\">Platformele suportate de Confluence<\/a><\/noindex>.<\/li>\n<\/ol>\n<h2>Arhitectura tehnic\u0103<\/h2>\n<p><img decoding=\"async\" alt=\"Cum s\u0103 implementa\u021bi Atlassian Jira + Confluence \u00een corpora\u021bii. Probleme tehnice\" src=\"\/wp-content\/uploads\/2020\/04\/db5bc14cb21c75671a5734586d5a7113.png\" style=\"display:block;margin: 0 auto;\"><\/p>\n<p>Explica\u021bii la schema:<\/p>\n<ul>\n<li>Schema prezint\u0103 implementarea \u00een banca noastr\u0103, aceast\u0103 configura\u021bie este oferit\u0103 ca exemplu \u0219i nu este recomandat\u0103.<\/li>\n<li>nginx ofer\u0103 func\u021bionalitatea de reverse-proxy at\u00e2t pentru Jira, c\u00e2t \u0219i pentru Confluence.<\/li>\n<li>Rezisten\u021ba SGBD-ului este realizat\u0103 prin intermediul capacit\u0103\u021bilor SGBD-ului.<\/li>\n<li>Transferul modific\u0103rilor \u00eentre medii se realizeaz\u0103 cu ajutorul pluginului Configuration Manager for Jira.<\/li>\n<li>AppSrv din schem\u0103 este un server de aplica\u021bii propriu pentru raportare, care nu utilizeaz\u0103 software-ul Atlassian.<\/li>\n<li>BD EasyBI este creat\u0103 pentru construirea cuburilor \u0219i raport\u0103rii folosind pluginul eazyBI Reports and Charts for Jira.<\/li>\n<li>Serviciul Confluence Synchrony (componenta care permite editarea simultan\u0103 a documentelor) nu este separat \u00een instala\u021bii distincte \u0219i este pornit \u00eempreun\u0103 cu Confluence, pe acela\u0219i server.<\/li>\n<\/ul>\n<h2>Licen\u021biere<\/h2>\n<p>\u00centreb\u0103rile legate de licen\u021bierea Atlassian merit\u0103 un articol separat, aici voi men\u021biona doar principiile generale.<br \/>\nPrincipalele \u00eentreb\u0103ri cu care ne-am confruntat sunt legate de licen\u021bierea edi\u021biilor Data Center. Caracteristicile licen\u021bierii pentru edi\u021biile Server \u0219i Data Center:<\/p>\n<ol>\n<li>Licen\u021ba pentru edi\u021bia Server este nelimitat\u0103 \u0219i cump\u0103r\u0103torul poate utiliza software-ul chiar \u0219i dup\u0103 expirarea licen\u021bei. Dar dup\u0103 expirarea licen\u021bei, cump\u0103r\u0103torul \u00ee\u0219i pierde dreptul de a primi suport pentru produs \u0219i de a actualiza software-ul la versiunile actuale.<\/li>\n<li>Licen\u021bierea se face \u00een func\u021bie de num\u0103rul de utilizatori din sistemul &#8216;JIRA Users&#8217; permis global. Nu conteaz\u0103 dac\u0103 ace\u0219tia folosesc sistemul sau nu \u2014 chiar dac\u0103 utilizatorii nu s-au logat niciodat\u0103 \u00een sistem, to\u021bi utilizatorii vor fi lua\u021bi \u00een considerare pentru licen\u021b\u0103. \u00cen cazul dep\u0103\u0219irii num\u0103rului de utilizatori licen\u021bia\u021bi, solu\u021bia va fi eliminarea permisiunii &#8216;JIRA Users&#8217; pentru unii utilizatori.<\/li>\n<li>Licen\u021ba pentru Data Center este de fapt un abonament. Este necesar\u0103 plata anual\u0103 a licen\u021bei. La expirarea termenului, utilizarea sistemului va fi blocat\u0103.<\/li>\n<li>Costul licen\u021belor poate varia \u00een timp. Dup\u0103 cum arat\u0103 experien\u021ba, de obicei \u00eentr-o direc\u021bie ascendent\u0103 \u0219i, posibil, semnificativ. Prin urmare, dac\u0103 \u00een acest an licen\u021bele au un anumit cost, anul urm\u0103tor pre\u021bul licen\u021belor poate cre\u0219te.<\/li>\n<li>Licen\u021bierea se realizeaz\u0103 pe utilizatori \u00een func\u021bie de tier (de exemplu, nivelul 1001-2000 utilizatori). Exist\u0103 posibilitatea de a trece la un tier superioar\u0103, cu o plat\u0103 suplimentar\u0103.<\/li>\n<li>\u00cen cazul dep\u0103\u0219irii num\u0103rului de utilizatori licen\u021bia\u021bi, noii utilizatori vor fi crea\u021bi f\u0103r\u0103 drept de acces \u00een sistem (&#8216;JIRA Users&#8217; permis global).<\/li>\n<li>Pluginurile pot fi licen\u021biate doar pentru acela\u0219i num\u0103r de utilizatori ca \u0219i software-ul principal.<\/li>\n<li>Licen\u021bierea este necesar\u0103 doar pentru instala\u021biile de produc\u021bie; pentru celelalte se poate ob\u021bine o licen\u021b\u0103 Developer: <noindex><a rel=\"nofollow\" href=\"https:\/\/confluence.atlassian.com\/jirakb\/get-a-developer-license-for-jira-server-744526918.html\">https:\/\/confluence.atlassian.com\/jirakb\/get-a-developer-license-for-jira-server-744526918.html<\/a><\/noindex>.<\/li>\n<li>Pentru achizi\u021bionarea suportului, este necesar\u0103 achizi\u021bionarea Renew Software maintenance \u2014 costul fiind de aproximativ 50% din costul software-ului ini\u021bial. Aceast\u0103 op\u021biune nu este disponibil\u0103 pentru Data Center \u0219i nu se aplic\u0103 pluginurilor \u2014 pentru suportul acestora va trebui s\u0103 pl\u0103ti\u021bi costul \u00eentreg anual.<br \/>\nAstfel, suportul anual pentru software cost\u0103 mai mult de 50% din pre\u021bul \u00eentreg al software-ului \u00een cazul edi\u021biei Server \u0219i 100% \u00een cazul edi\u021biei Data Center \u2014 aceasta este semnificativ mai mult dec\u00e2t la majoritatea altor furnizori. Din punctul meu de vedere, acesta este un dezavantaj major al modelului de afaceri Atlassian.<\/li>\n<\/ol>\n<p>Particularit\u0103\u021bile tranzi\u021biei de la edi\u021bia Server la Data Center:<\/p>\n<ol>\n<li>Tranzi\u021bia de la edi\u021bia Server la Data Center este pl\u0103tit\u0103. Costul \u00eel pute\u021bi g\u0103si aici <noindex><a rel=\"nofollow\" href=\"https:\/\/www.atlassian.com\/licensing\/data-center\">https:\/\/www.atlassian.com\/licensing\/data-center<\/a><\/noindex>.<\/li>\n<li>\u00cen cazul tranzi\u021biei de la edi\u021bia Server la Data Center, nu este necesar\u0103 plata pentru schimbarea edi\u021biei la pluginuri \u2014 pluginurile pentru edi\u021bia Server vor func\u021biona. \u00cens\u0103, va fi necesar s\u0103 re\u00eennoi\u021bi licen\u021bele pentru pluginuri pentru edi\u021bia Data Center.<\/li>\n<li>Pute\u021bi utiliza pluginuri pentru care nu exist\u0103 versiune pentru edi\u021biile Data Center. Totu\u0219i, aceste pluginuri pot func\u021biona necorespunz\u0103tor, a\u0219a c\u0103 este mai bine s\u0103 preconiz\u0103m o alternativ\u0103 pentru aceste pluginuri.<\/li>\n<li>Trecerea la edi\u021bia Data Center se face prin instalarea unei noi licen\u021be. Licen\u021ba pentru edi\u021bia Server r\u0103m\u00e2ne \u00een continuare disponibil\u0103.<\/li>\n<li>Nu exist\u0103 nicio diferen\u021b\u0103 func\u021bional\u0103 \u00eentre edi\u021biile Data Center \u0219i Server pentru utilizatori; toate diferen\u021bele sunt doar \u00een func\u021biile de administrare \u0219i \u00een capacit\u0103\u021bile tehnice de instalare.<\/li>\n<li>Costul software-ului \u0219i al pluginurilor variaz\u0103 pentru edi\u021biile Server \u0219i Data Center. Diferen\u021ba de pre\u021b este adesea de sub 5% (nu este semnificativ\u0103). Un exemplu de calcul al costului este prezentat mai jos.<\/li>\n<\/ol>\n<h2>Volumul func\u021bional al implement\u0103rii<\/h2>\n<p>Pachetul de baz\u0103 al software-ului Atlassian include un num\u0103r mare de func\u021bionalit\u0103\u021bi, dar adesea func\u021biile oferite de sistem sunt foarte insuficiente. Uneori, chiar \u0219i cele mai simple func\u021bii nu sunt disponibile \u00een pachetul de baz\u0103, a\u0219a c\u0103 nu se poate evita utilizarea pluginurilor \u00een aproape orice implementare. Pentru sistemul Jira, folosim urm\u0103toarele pluginuri (imaginea este clicabil\u0103):<br \/>\n<noindex><a rel=\"nofollow\" href=\"https:\/\/habrastorage.org\/webt\/42\/un\/i4\/42uni4jlnzbsvva8eteibtbcndq.jpeg\"><img decoding=\"async\" alt=\"Cum s\u0103 implementa\u021bi Atlassian Jira + Confluence \u00een corpora\u021bii. Probleme tehnice\" src=\"\/wp-content\/uploads\/2020\/04\/487af50599537e78b599296fce99bfff.png\" style=\"display:block;margin: 0 auto;\"><\/a><\/noindex><\/p>\n<p>Pentru sistemul Confluence, folosim urm\u0103toarele pluginuri (imaginea este clicabil\u0103):<br \/>\n<noindex><a rel=\"nofollow\" href=\"https:\/\/habrastorage.org\/webt\/kq\/i3\/ne\/kqi3neplj6jwfi-piuqxc77tysw.jpeg\"><img decoding=\"async\" alt=\"Cum s\u0103 implementa\u021bi Atlassian Jira + Confluence \u00een corpora\u021bii. Probleme tehnice\" src=\"\/wp-content\/uploads\/2020\/04\/59e1884af4a166c2f2211adf361bbf3a.png\" style=\"display:block;margin: 0 auto;\"><\/a><\/noindex><\/p>\n<p>Comentarii la tabele cu pluginuri:<\/p>\n<ul>\n<li>Toate pre\u021burile sunt calculate pe baza a 2000 de utilizatori;<\/li>\n<li>Pre\u021burile sunt bazate pe pre\u021burile indicate <noindex><a rel=\"nofollow\" href=\"https:\/\/marketplace.atlassian.com\">https:\/\/marketplace.atlassian.com<\/a><\/noindex>, costul real (cu discounturi) este mai mic;<\/li>\n<li>A\u0219a cum vedem, suma total\u0103 nu difer\u0103 practic \u00eentre edi\u021biile Data Center \u0219i Server;<\/li>\n<li>Pentru utilizare, am selectat doar pluginuri care sunt compatibile cu edi\u021bia Data Center. Celelalte pluginuri au fost excluse din planuri, pentru stabilitatea sistemului.<\/li>\n<\/ul>\n<p>Func\u021bionalitatea este descris\u0103 pe scurt \u00een coloana Comentariu. Pluginurile suplimentare au extins func\u021bionalitatea sistemului:<\/p>\n<ul>\n<li>Ad\u0103ugate c\u00e2teva instrumente vizuale;<\/li>\n<li>Mecanismele de integrare au fost \u00eembun\u0103t\u0103\u021bite;<\/li>\n<li>Ad\u0103ugat instrumentar pentru proiecte bazate pe modelul Waterfall;<\/li>\n<li>Ad\u0103ugat instrumentar pentru Scrum scalabil, pentru organizarea muncii \u00een echipe mari de proiect;<\/li>\n<li>Ad\u0103ugat func\u021bionalitate pentru gestionarea timpului;<\/li>\n<li>Ad\u0103ugat instrumentar pentru automatizarea opera\u021biunilor \u0219i configurarea solu\u021biei;<\/li>\n<li>Ad\u0103ugat\u0103 func\u021bionalitate pentru simplificarea \u0219i automatizarea administr\u0103rii solu\u021biei.<\/li>\n<\/ul>\n<p>De asemenea, folosim <noindex><a rel=\"nofollow\" href=\"https:\/\/confluence.atlassian.com\/doc\/atlassian-companion-app-release-notes-958455712.html\"><b>Atlassian Companion app<\/b><\/a><\/noindex>. Aceast\u0103 aplica\u021bie permite editarea fi\u0219ierelor \u00een aplica\u021bii externe (MS Office) \u0219i returnarea acestora \u00eenapoi \u00een Confluence (check-in).<br \/>\nAplica\u021bie pentru locurile de munc\u0103 ale utilizatorilor (client gros) <b>ALM Works Jira Client<\/b> <noindex><a rel=\"nofollow\" href=\"https:\/\/marketplace.atlassian.com\/apps\/7070\">https:\/\/marketplace.atlassian.com\/apps\/7070<\/a><\/noindex> am decis s\u0103 nu o folosim din cauza suportului slab din partea furnizorului \u0219i a feedback-ului negativ.<br \/>\nPentru <b>integr\u0103ri cu MS Project<\/b> noi folosim o aplica\u021bie personalizat\u0103 care permite actualizarea statutelor Issue \u00een MS Project din Jira \u0219i invers. \u00cen viitor, pentru acelea\u0219i scopuri, pl\u0103nuim s\u0103 folosim un plugin pl\u0103tit <noindex><a rel=\"nofollow\" href=\"https:\/\/marketplace.atlassian.com\/apps\/9203\">Ceptah Bridge \u2014 JIRA MS Project Plugin<\/a><\/noindex>, care se instaleaz\u0103 ca un add-on \u00een MS Project.<br \/>\n<b>Integr\u0103rile cu aplica\u021bii externe<\/b> sunt realizate prin Application Links. Astfel, pentru aplica\u021biile Atlassian, integr\u0103rile sunt preconfigurate \u0219i func\u021bioneaz\u0103 imediat dup\u0103 setare, de exemplu, se poate afi\u0219a pe pagina din Confluence informa\u021bii despre Issues \u00een Jira.<br \/>\nPentru accesul la serverele Jira \u0219i Confluence se folose\u0219te REST API: <noindex><a rel=\"nofollow\" href=\"https:\/\/developer.atlassian.com\/server\/jira\/platform\/rest-apis\">https:\/\/developer.atlassian.com\/server\/jira\/platform\/rest-apis<\/a><\/noindex>.<br \/>\nSOAP \u0219i XML-RPC API au fost desprinse \u0219i nu mai sunt disponibile \u00een versiunile noi pentru utilizare.<\/p>\n<h2>Concluzie<\/h2>\n<p>A\u0219adar, am analizat caracteristicile tehnice ale implement\u0103rii sistemului bazat pe produsele Atlassian. Solu\u021bia propus\u0103 reprezint\u0103 una dintre solu\u021biile posibile \u0219i se potrive\u0219te bine pentru un mediu corporativ<\/p>\n<p>Solu\u021bia propus\u0103 este scalabil\u0103, cu toleran\u021b\u0103 la erori, cuprinde trei medii pentru organizarea dezvolt\u0103rii \u0219i test\u0103rii, con\u021bine toate elementele necesare pentru colaborarea \u00een sistem \u0219i ofer\u0103 o gam\u0103 larg\u0103 de instrumente pentru gestionarea proiectelor.<\/p>\n<p>Voi r\u0103spunde cu pl\u0103cere la \u00eentreb\u0103ri \u00een comentarii.<\/p>\n<p>Sursa: <a content=\"nofollow\" rel=\"nofollow\" href=\"https:\/\/habr.com\/ru\/post\/499474\/\">habr.com<\/a><\/p>","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"excerpt":{"rendered":"<p>\u041f\u043b\u0430\u043d\u0438\u0440\u0443\u0435\u0442\u0435 \u0432\u043d\u0435\u0434\u0440\u0435\u043d\u0438\u0435 \u041f\u041e Atlassian (Jira, Confluence)? \u041d\u0435 \u0445\u043e\u0442\u0438\u0442\u0435 \u0434\u043e\u043f\u0443\u0441\u0442\u0438\u0442\u044c \u0436\u0435\u0441\u0442\u043e\u043a\u0438\u0445 \u043e\u0448\u0438\u0431\u043e\u043a \u0432 \u043f\u0440\u043e\u0435\u043a\u0442\u0438\u0440\u043e\u0432\u0430\u043d\u0438\u0438, \u043a\u043e\u0442\u043e\u0440\u044b\u0435 \u043f\u043e\u0442\u043e\u043c \u043f\u0440\u0438\u0434\u0451\u0442\u0441\u044f \u0440\u0435\u0448\u0430\u0442\u044c \u0432 \u043f\u043e\u0441\u043b\u0435\u0434\u043d\u0438\u0439 \u043c\u043e\u043c\u0435\u043d\u0442? \u0422\u043e\u0433\u0434\u0430 \u0432\u0430\u043c \u0441\u044e\u0434\u0430 \u2014 \u0440\u0430\u0441\u0441\u043c\u0430\u0442\u0440\u0438\u0432\u0430\u0435\u043c \u0432\u043d\u0435\u0434\u0440\u0435\u043d\u0438\u0435 Atlassian Jira + Confluence \u0432 \u043a\u043e\u0440\u043f\u043e\u0440\u0430\u0446\u0438\u0438 \u0441 \u0443\u0447\u0451\u0442\u043e\u043c \u0440\u0430\u0437\u043b\u0438\u0447\u043d\u044b\u0445 \u0442\u0435\u0445\u043d\u0438\u0447\u0435\u0441\u043a\u0438\u0445 \u0430\u0441\u043f\u0435\u043a\u0442\u043e\u0432. \u0417\u0434\u0440\u0430\u0432\u0441\u0442\u0432\u0443\u0439\u0442\u0435, \u044f \u044f\u0432\u043b\u044f\u044e\u0441\u044c \u0412\u043b\u0430\u0434\u0435\u043b\u044c\u0446\u0435\u043c \u043f\u0440\u043e\u0434\u0443\u043a\u0442\u0430 \u0432 \u0420\u0421\u0425\u0411 \u0438 \u043e\u0442\u0432\u0435\u0447\u0430\u044e \u0437\u0430 \u0440\u0430\u0437\u0432\u0438\u0442\u0438\u0435 \u0421\u0438\u0441\u0442\u0435\u043c\u044b \u0443\u043f\u0440\u0430\u0432\u043b\u0435\u043d\u0438\u044f \u0436\u0438\u0437\u043d\u0435\u043d\u043d\u044b\u043c \u0446\u0438\u043a\u043b\u043e\u043c (\u0421\u0423\u0416\u0426) \u043f\u043e\u0441\u0442\u0440\u043e\u0435\u043d\u043d\u043e\u0439 \u043d\u0430 [&hellip;]<\/p>\n","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"author":1,"featured_media":79685,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[688],"tags":[],"class_list":["post-79684","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-administrirovanie"],"aioseo_notices":[],"aioseo_head":"\n\t\t<!-- All in One SEO 5.0.4 - aioseo.com -->\n\t<meta name=\"description\" content=\"\u041f\u043b\u0430\u043d\u0438\u0440\u0443\u0435\u0442\u0435 \u0432\u043d\u0435\u0434\u0440\u0435\u043d\u0438\u0435 \u041f\u041e Atlassian (Jira, Confluence)? \u041d\u0435 \u0445\u043e\u0442\u0438\u0442\u0435 \u0434\u043e\u043f\u0443\u0441\u0442\u0438\u0442\u044c \u0436\u0435\u0441\u0442\u043e\u043a\u0438\u0445 \u043e\u0448\u0438\u0431\u043e\u043a \u0432 \u043f\u0440\u043e\u0435\u043a\u0442\u0438\u0440\u043e\u0432\u0430\u043d\u0438\u0438, \u043a\u043e\u0442\u043e\u0440\u044b\u0435 \u043f\u043e\u0442\u043e\u043c \u043f\u0440\u0438\u0434\u0451\u0442\u0441\u044f \u0440\u0435\u0448\u0430\u0442\u044c \u0432 \u043f\u043e\u0441\u043b\u0435\u0434\u043d\u0438\u0439 \u043c\u043e\u043c\u0435\u043d\u0442?\" \/>\n\t<meta name=\"robots\" content=\"max-image-preview:large\" \/>\n\t<meta name=\"author\" content=\"Yuri Gagarin\"\/>\n\t<link rel=\"canonical\" href=\"https:\/\/prohoster.info\/ro\/blog\/administrirovanie\/kak-vnedrit-atlassian-jira-confluence-v-korporaczii-tehnicheskie-voprosy\" \/>\n\t\t<meta name=\"generator\" content=\"All in One SEO (AIOSEO) 5.0.4\" \/>\n\t\t<meta property=\"og:locale\" content=\"ro_RO\" \/>\n\t\t<meta property=\"og:site_name\" content=\"ProHoster | \u041a\u0443\u043f\u0438\u0442\u044c \u043d\u0430\u0434\u0435\u0436\u043d\u044b\u0439 \u0445\u043e\u0441\u0442\u0438\u043d\u0433 \u0434\u043b\u044f \u0441\u0430\u0439\u0442\u043e\u0432 \u0441 \u0437\u0430\u0449\u0438\u0442\u043e\u0439 \u043e\u0442 DDoS, VPS VDS \u0441\u0435\u0440\u0432\u0435\u0440\u044b\" \/>\n\t\t<meta property=\"og:type\" content=\"article\" \/>\n\t\t<meta property=\"og:title\" content=\"\ud83e\udd47\u041a\u0430\u043a \u0432\u043d\u0435\u0434\u0440\u0438\u0442\u044c Atlassian Jira + Confluence \u0432 \u043a\u043e\u0440\u043f\u043e\u0440\u0430\u0446\u0438\u0438. \u0422\u0435\u0445\u043d\u0438\u0447\u0435\u0441\u043a\u0438\u0435 \u0432\u043e\u043f\u0440\u043e\u0441\u044b | ProHoster\" \/>\n\t\t<meta property=\"og:description\" content=\"\u041f\u043b\u0430\u043d\u0438\u0440\u0443\u0435\u0442\u0435 \u0432\u043d\u0435\u0434\u0440\u0435\u043d\u0438\u0435 \u041f\u041e Atlassian (Jira, Confluence)? \u041d\u0435 \u0445\u043e\u0442\u0438\u0442\u0435 \u0434\u043e\u043f\u0443\u0441\u0442\u0438\u0442\u044c \u0436\u0435\u0441\u0442\u043e\u043a\u0438\u0445 \u043e\u0448\u0438\u0431\u043e\u043a \u0432 \u043f\u0440\u043e\u0435\u043a\u0442\u0438\u0440\u043e\u0432\u0430\u043d\u0438\u0438, \u043a\u043e\u0442\u043e\u0440\u044b\u0435 \u043f\u043e\u0442\u043e\u043c \u043f\u0440\u0438\u0434\u0451\u0442\u0441\u044f \u0440\u0435\u0448\u0430\u0442\u044c \u0432 \u043f\u043e\u0441\u043b\u0435\u0434\u043d\u0438\u0439 \u043c\u043e\u043c\u0435\u043d\u0442?\" \/>\n\t\t<meta property=\"og:url\" content=\"https:\/\/prohoster.info\/ro\/blog\/administrirovanie\/kak-vnedrit-atlassian-jira-confluence-v-korporaczii-tehnicheskie-voprosy\" \/>\n\t\t<meta property=\"og:image\" content=\"https:\/\/prohoster.info\/wp-content\/uploads\/2021\/11\/logo-350.jpg\" \/>\n\t\t<meta property=\"og:image:secure_url\" content=\"https:\/\/prohoster.info\/wp-content\/uploads\/2021\/11\/logo-350.jpg\" \/>\n\t\t<meta property=\"og:image:width\" content=\"350\" \/>\n\t\t<meta property=\"og:image:height\" content=\"350\" \/>\n\t\t<meta property=\"article:published_time\" content=\"2020-04-29T17:42:05+00:00\" \/>\n\t\t<meta property=\"article:modified_time\" content=\"2021-01-02T11:04:34+00:00\" \/>\n\t\t<meta property=\"article:publisher\" content=\"https:\/\/www.facebook.com\/prohoster\" \/>\n\t\t<meta property=\"article:author\" content=\"https:\/\/www.facebook.com\/prohoster\" \/>\n\t\t<!-- All in One SEO -->\n\n","aioseo_head_json":{"title":"\ud83e\udd47Cum s\u0103 implementa\u021bi Atlassian Jira + Confluence \u00een corpora\u021bii. \u00centreb\u0103ri tehnice | ProHoster","description":"Planifica\u021bi implementarea software-ului Atlassian (Jira, Confluence)? Nu dori\u021bi s\u0103 face\u021bi gre\u0219eli grave \u00een proiectare, care vor trebui rezolvate \u00een ultimul moment?","canonical_url":"https:\/\/prohoster.info\/ro\/blog\/administrirovanie\/kak-vnedrit-atlassian-jira-confluence-v-korporaczii-tehnicheskie-voprosy","robots":"max-image-preview:large","keywords":"","webmasterTools":{"miscellaneous":""},"schema":null,"og:locale":"ro_RO","og:site_name":"ProHoster | \u041a\u0443\u043f\u0438\u0442\u044c \u043d\u0430\u0434\u0435\u0436\u043d\u044b\u0439 \u0445\u043e\u0441\u0442\u0438\u043d\u0433 \u0434\u043b\u044f \u0441\u0430\u0439\u0442\u043e\u0432 \u0441 \u0437\u0430\u0449\u0438\u0442\u043e\u0439 \u043e\u0442 DDoS, VPS VDS \u0441\u0435\u0440\u0432\u0435\u0440\u044b","og:type":"article","og:title":"\ud83e\udd47\u041a\u0430\u043a \u0432\u043d\u0435\u0434\u0440\u0438\u0442\u044c Atlassian Jira + Confluence \u0432 \u043a\u043e\u0440\u043f\u043e\u0440\u0430\u0446\u0438\u0438. \u0422\u0435\u0445\u043d\u0438\u0447\u0435\u0441\u043a\u0438\u0435 \u0432\u043e\u043f\u0440\u043e\u0441\u044b | ProHoster","og:description":"\u041f\u043b\u0430\u043d\u0438\u0440\u0443\u0435\u0442\u0435 \u0432\u043d\u0435\u0434\u0440\u0435\u043d\u0438\u0435 \u041f\u041e Atlassian (Jira, Confluence)? \u041d\u0435 \u0445\u043e\u0442\u0438\u0442\u0435 \u0434\u043e\u043f\u0443\u0441\u0442\u0438\u0442\u044c \u0436\u0435\u0441\u0442\u043e\u043a\u0438\u0445 \u043e\u0448\u0438\u0431\u043e\u043a \u0432 \u043f\u0440\u043e\u0435\u043a\u0442\u0438\u0440\u043e\u0432\u0430\u043d\u0438\u0438, \u043a\u043e\u0442\u043e\u0440\u044b\u0435 \u043f\u043e\u0442\u043e\u043c \u043f\u0440\u0438\u0434\u0451\u0442\u0441\u044f \u0440\u0435\u0448\u0430\u0442\u044c \u0432 \u043f\u043e\u0441\u043b\u0435\u0434\u043d\u0438\u0439 \u043c\u043e\u043c\u0435\u043d\u0442?","og:url":"https:\/\/prohoster.info\/ro\/blog\/administrirovanie\/kak-vnedrit-atlassian-jira-confluence-v-korporaczii-tehnicheskie-voprosy","og:image":"https:\/\/prohoster.info\/wp-content\/uploads\/2021\/11\/logo-350.jpg","og:image:secure_url":"https:\/\/prohoster.info\/wp-content\/uploads\/2021\/11\/logo-350.jpg","og:image:width":350,"og:image:height":350,"article:published_time":"2020-04-29T17:42:05+00:00","article:modified_time":"2021-01-02T11:04:34+00:00","article:publisher":"https:\/\/www.facebook.com\/prohoster","article:author":"https:\/\/www.facebook.com\/prohoster"},"aioseo_meta_data":{"post_id":"79684","title":null,"description":"","keywords":"","keyphrases":null,"primary_term":null,"canonical_url":"","og_title":null,"og_description":null,"og_object_type":"default","og_image_type":"default","og_image_url":null,"og_image_width":null,"og_image_height":null,"og_image_custom_url":null,"og_image_custom_fields":null,"og_video":null,"og_custom_url":null,"og_article_section":null,"og_article_tags":null,"twitter_use_og":false,"twitter_card":"default","twitter_image_type":"default","twitter_image_url":null,"twitter_image_custom_url":null,"twitter_image_custom_fields":null,"twitter_title":null,"twitter_description":null,"schema":{"blockGraphs":[],"customGraphs":[],"default":{"data":{"Article":[],"Course":[],"Dataset":[],"FAQPage":[],"Movie":[],"Person":[],"Product":[],"ProductReview":[],"Car":[],"Recipe":[],"Service":[],"SoftwareApplication":[],"WebPage":[]},"graphName":"","isEnabled":true},"graphs":[]},"schema_type":null,"schema_type_options":null,"pillar_content":false,"robots_default":true,"robots_noindex":false,"robots_noarchive":false,"robots_nosnippet":false,"robots_nofollow":false,"robots_noimageindex":false,"robots_noodp":false,"robots_notranslate":false,"robots_max_snippet":null,"robots_max_videopreview":null,"robots_max_imagepreview":"large","priority":null,"frequency":null,"local_seo":null,"seo_analyzer_scan_date":null,"breadcrumb_settings":null,"limit_modified_date":false,"reviewed_by":null,"ai":null,"created":"2021-02-28 10:07:34","updated":"2022-09-29 22:22:30","focus_keyword":null,"additional_keywords":null,"truseo_locale":null},"gt_translate_keys":[{"key":"link","format":"url"}],"_links":{"self":[{"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/posts\/79684","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/comments?post=79684"}],"version-history":[{"count":0,"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/posts\/79684\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/media\/79685"}],"wp:attachment":[{"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/media?parent=79684"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/categories?post=79684"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/tags?post=79684"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}