Date: Thu, 28 Mar 2024 21:27:19 +0800 (CST) Message-ID: <1938783602.254.1711632439460@99a00c216ff6> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_253_1760799712.1711632439459" ------=_Part_253_1760799712.1711632439459 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
JIRA 6.3=E6=9C=89=E5=8A=
=A9=E4=BA=8E=E5=9B=A2=E9=98=9F=E7=9A=84=E5=B7=A5=E4=BD=9C=E6=95=88=E7=8E=87=
=E5=92=8C=E6=95=88=E6=9E=9C
In JIRA 6.3, we've introduce=
d several key concepts and features to ensure that this version of JIRA is =
the most robust and efficient yet. With JIRA Data Center, we have improved =
availability for mission critical instances. Our Github importer, inline ve=
rsion and component creation, and auditing options make JIRA easier to admi=
nister. And your teams will be more productive with features like inline is=
sue creation and streamlined user interface.
We're still working on further JIRA integration with your favorite Atlas= sian coding tools, and further improvements to your team's visibility and c= ontrol of their code is coming soon! Watch this page....
<=
span style=3D"color: rgb(0,0,0);">
=
JIRA 6.3=E6=96=B0=E7=89=
=B9=E6=80=A7
We've built upon all the features = that make JIRA great for your business at scale and created a new offering = specifically for organizations that require high availability for mission c= ritical JIRA instances. These features are enabled through the clustering c= apability in JIRA Data Center 6.3:
You can access these features in J= IRA 6.3 by purchasing a JIRA Data Center license. Read more about JIRA Data Center here...
Sitting in a planning meeting and want to create an issue in the moment?= Easy! With inline issue creation and JIRA Agile, you can now create an iss= ue from within your Scrum board during planning. Simply click on the <= strong>Create issue link, select the issue type and enter a b= rief summary, then hit the Enter button. The issue is created and automatic= ally added to your backlog. It couldn't be simpler!
Project administrators can now add versions and components from within t= he Fix Version/s, Affected Version/s and Component/s fields. Previously, p= roject administrators needed to add a version or component via the appropri= ate screen on the project's administration page. Now, project administrator= s are able to create a version or component by typing it in the appropriate= field, and selecting it from the drop-down list. When you begin typing tex= t that JIRA does not recognize as existing, it will add it to the bottom of= the drop-down list and add (New Version) or (New Component). Selecting the= new version or component will automatically create it within your project = for future use.
We first introduced the audit log in JIRA 6.1 late last year. In this release, we= 've added some new features to the audit log to make it more efficient and = easier to use:
The newly released GitHub importer allows you to connect to your GitHub = account, regardless of whether it's a private or enterprise account, and im= port any public, private or starred repository configurations into JIRA. Yo= u can map the GitHub labels to issue types, to resolutions, or import them = as JIRA labels. The import process supports importing attachments, and= also provides you with a detailed log of your import so that you can = troubleshoot any issues.
Of course, that's not all we've done in this release! We've been working= hard to improve the user experience, and to make sure that whatever Atlass= ian product you use, you recognize that great Atlassian "feel".