#NLS_ENCODING=UTF-8
#NLS_MESSAGEFORMAT_NONE
All\ Epics\ will\ be\ imported\ as\ initiatives,\ and\ all\ linked\ issues\ will\ be\ added\ to\ this\ initiative=All Epics will be imported as initiatives, and all linked issues will be added to this initiative~ucr-plugin-jira1
All\ issues\ of\ the\ specified\ issue\ type\ will\ be\ imported\ as\ initiatives,\ and\ all\ linked\ issues\ will\ be\ added\ to\ this\ initiative=All issues of the specified issue type will be imported as initiatives, and all linked issues will be added to this initiative~ucr-plugin-jira2
Allowed\ Custom\ Fields\ Select.\ Default,\ Textbox,\ and\ Single\ Select.=Allowed Custom Fields Select. Default, Textbox, and Single Select.~ucr-plugin-jira3
Application\ Mapping=Application Mapping~ucr-plugin-jira4
Auto\ Map\ Applications=Auto Map Applications~ucr-plugin-jira5
Auto\ Map\ Releases=Auto Map Releases~ucr-plugin-jira6
Change=Change~ucr-plugin-jira7
Check\ this\ box\ to\ create\ Initiatives\ in\ UrbanCode\ Release\ if\ they\ do\ not\ exist.=Check this box to create Initiatives in UrbanCode Release if they do not exist.~ucr-plugin-jira8
Child\ Link\ Depth\ (integer)=Child Link Depth (integer)~ucr-plugin-jira9
Click\ to\ check\ the\ connection\ to\ the\ JIRA\ server.=Click to check the connection to the JIRA server.~ucr-plugin-jira10
Click\ to\ delete\ all\ items\ that\ were\ retrieved\ from\ the\ integration.=Click to delete all items that were retrieved from the integration.~ucr-plugin-jira11
Configuring\ an\ integration\ provider\ for\ JIRA=Configuring an integration provider for JIRA~ucr-plugin-jira12
Create\ New\ Initiatives=Create New Initiatives~ucr-plugin-jira13
Create\ Releases\ from\ Jira\ Releases\ (Fix\ Versions)=Create Releases from Jira Releases (Fix Versions)~ucr-plugin-jira14
Custom\ Auto\ Map\ Initiatives=Custom Auto Map Initiatives~ucr-plugin-jira15
Custom\ Issue\ Type\ (Name)=Custom Issue Type (Name)~ucr-plugin-jira16
Custom\ Issue\ Types\ as\ Initiatives=Custom Issue Types as Initiatives~ucr-plugin-jira17
Epics\ as\ Initiatives=Epics as Initiatives~ucr-plugin-jira18
Full\ Integration=Full Integration~ucr-plugin-jira19
HTTP\ Proxy\ Host=HTTP Proxy Host~ucr-plugin-jira20
HTTP\ Proxy\ Password=HTTP Proxy Password~ucr-plugin-jira21
HTTP\ Proxy\ Port=HTTP Proxy Port~ucr-plugin-jira22
HTTP\ Proxy\ Username=HTTP Proxy Username~ucr-plugin-jira23
If\ importing\ a\ custom\ issue\ type\ as\ an\ initiative\ is\ more\ suitable\ than\ importing\ epics\ as\ initiatives,\ you\ may\ specify\ the\ issue\ type\ here.\ You\ may\ also\ specify\ the\ issue\ link\ type\ that\ is\ used\ to\ import\ child\ changes.=If importing a custom issue type as an initiative is more suitable than importing epics as initiatives, you may specify the issue type here. You may also specify the issue link type that is used to import child changes.~ucr-plugin-jira24
Import\ a\ Custom\ Issue\ Type\ as\ Initiatives=Import a Custom Issue Type as Initiatives~ucr-plugin-jira25
Import\ Epics\ as\ Initiatives=Import Epics as Initiatives~ucr-plugin-jira26
Initiative\ Auto\ Mapping=Initiative Auto Mapping~ucr-plugin-jira27
Integration=Integration~ucr-plugin-jira28
Issue\ Link\ (Name)\ for\ Child\ Changes=Issue Link (Name) for Child Changes~ucr-plugin-jira29
JIRA\ Base\ URL=JIRA Base URL~ucr-plugin-jira30
JIRA\ Integration=JIRA Integration~ucr-plugin-jira31
JIRA\ Password=JIRA Password~ucr-plugin-jira32
JIRA\ Plug-in=JIRA Plug-in~ucr-plugin-jira33
JIRA\ Username=JIRA Username~ucr-plugin-jira34
JiraFields=JiraFields~ucr-plugin-jira35
JiraPriorities=JiraPriorities~ucr-plugin-jira36
JiraProjects=JiraProjects~ucr-plugin-jira37
JiraProjectsOnly=JiraProjectsOnly~ucr-plugin-jira38
JiraStatuses=JiraStatuses~ucr-plugin-jira39
JiraTypes=JiraTypes~ucr-plugin-jira40
Ping\ the\ JIRA\ Server=Ping the JIRA Server~ucr-plugin-jira41
PingServerButton=PingServerButton~ucr-plugin-jira42
Priorities\ Select=Priorities Select~ucr-plugin-jira43
Project\ Select=Project Select~ucr-plugin-jira44
Provide\ the\ hostname\ of\ the\ HTTP\ proxy\ to\ use\ to\ connect\ to\ JIRA.\ Eg\ proxy.domain.com=Provide the hostname of the HTTP proxy to use to connect to JIRA. Eg proxy.domain.com~ucr-plugin-jira45
Provide\ the\ password\ to\ authenticate\ with\ HTTP\ proxy.=Provide the password to authenticate with HTTP proxy.~ucr-plugin-jira46
Provide\ the\ port\ number\ of\ the\ HTTP\ proxy\ to\ use\ to\ connect\ to\ JIRA.=Provide the port number of the HTTP proxy to use to connect to JIRA.~ucr-plugin-jira47
Provide\ the\ username\ to\ authenticate\ with\ HTTP\ proxy.=Provide the username to authenticate with HTTP proxy.~ucr-plugin-jira48
Release\ Auto\ Mapping=Release Auto Mapping~ucr-plugin-jira49
Remove\ all\ imported\ issues=Remove all imported issues~ucr-plugin-jira50
ResetButton=ResetButton~ucr-plugin-jira51
Select\ the\ JIRA\ field\ to\ map\ to\ Initiatives\ in\ UrbanCode\ Release.=Select the JIRA field to map to Initiatives in UrbanCode Release.~ucr-plugin-jira52
Select\ the\ JIRA\ field\ to\ map\ to\ Releases\ in\ UrbanCode\ Release.=Select the JIRA field to map to Releases in UrbanCode Release.~ucr-plugin-jira53
Select\ the\ standard\ or\ custom\ JIRA\ field\ to\ map\ to\ Applications\ in\ UrbanCode\ Release.\ It\ is\ suggested\ that\ the\ `Project`\ or\ `Component/s`\ field\ is\ specified.=Select the standard or custom JIRA field to map to Applications in UrbanCode Release. It is suggested that the `Project` or `Component/s` field is specified.~ucr-plugin-jira54
Select\ to\ run\ the\ complete\ integration\ regardless\ of\ the\ time\ last\ run.=Select to run the complete integration regardless of the time last run.~ucr-plugin-jira55
Specify\ any\ Text\ or\ Single\ Select\ field\ to\ automatically\ map\ to\ an\ initiative\ in\ UrbanCode\ Release\ using\ the\ custom\ auto\ map\ dropdown.\ JIRA\ values\ must\ be\ a\ single\ string\ of\ name\ and\ ID\ separated\ by\ an\ underscore\ or\ colon.\ The\ custom\ mapping\ first\ uses\ the\ ID\ to\ determine\ whether\ a\ matching\ Initiative\ ID\ exists,\ and\ otherwise\ uses\ the\ name.\ If\ the\ initiative\ does\ not\ exist,\ the\ Initiative\ field\ for\ the\ change\ in\ UrbanCode\ Release\ is\ left\ blank.=Specify any Text or Single Select field to automatically map to an initiative in UrbanCode Release using the custom auto map dropdown. JIRA values must be a single string of name and ID separated by an underscore or colon. The custom mapping first uses the ID to determine whether a matching Initiative ID exists, and otherwise uses the name. If the initiative does not exist, the Initiative field for the change in UrbanCode Release is left blank.~ucr-plugin-jira56
Specify\ any\ Text\ or\ Single\ Select\ field\ to\ automatically\ map\ to\ an\ UrbanCode\ Release\ application\ using\ the\ custom\ auto\ map\ dropdown.\ (The\ `Component/s`\ field\ is\ the\ only\ exception\ to\ the\ Text\ or\ Single\ Select\ field\ rule.)\ JIRA\ custom\ values\ must\ take\ the\ form\ `[ID\:]Name`.\ Use\ the\ manual\ Application\ Mapping\ boxes\ to\ have\ maximum\ control\ over\ the\ desired\ Application\ and\ Project/Component\ pairs.\ If\ an\ issue\ has\ more\ than\ one\ matching\ component,\ a\ change\ for\ each\ component\ will\ be\ created.\ Most\ commonly,\ JIRA\ plug-in\ users\ will\ utilize\ the\ `Project`\ or\ `Component/s`\ field.\ If\ an\ Auto\ Map\ field\ is\ specified,\ the\ manually\ mapped\ values\ will\ be\ ignored.=Specify any Text or Single Select field to automatically map to an UrbanCode Release application using the custom auto map dropdown. (The `Component/s` field is the only exception to the Text or Single Select field rule.) JIRA custom values must take the form `[ID\:]Name`. Use the manual Application Mapping boxes to have maximum control over the desired Application and Project/Component pairs. If an issue has more than one matching component, a change for each component will be created. Most commonly, JIRA plug-in users will utilize the `Project` or `Component/s` field. If an Auto Map field is specified, the manually mapped values will be ignored.~ucr-plugin-jira57
Specify\ any\ Text\ or\ Single\ Select\ JIRA\ field\ to\ automatically\ map\ to\ a\ release\ in\ UrbanCode\ Release\ using\ the\ Release\ Auto\ Map\ dropdown.\ (The\ `Fix\ Version/s`\ field\ is\ the\ only\ exception\ to\ the\ Text\ or\ Single\ Select\ field\ rule.)\ JIRA\ values\ must\ be\ a\ single\ string\ of\ name\ and\ ID\ separated\ by\ an\ underscore\ or\ colon.\ The\ auto\ mapping\ first\ uses\ the\ ID\ to\ determine\ whether\ a\ matching\ Release\ ID\ exists,\ and\ otherwise\ uses\ the\ name.\ Only\ JIRA\ issues\ with\ a\ corresponding\ release\ will\ be\ imported.\ Most\ commonly,\ JIRA\ plug-in\ users\ will\ utilize\ the\ `Fix\ Version/s`\ field.=Specify any Text or Single Select JIRA field to automatically map to a release in UrbanCode Release using the Release Auto Map dropdown. (The `Fix Version/s` field is the only exception to the Text or Single Select field rule.) JIRA values must be a single string of name and ID separated by an underscore or colon. The auto mapping first uses the ID to determine whether a matching Release ID exists, and otherwise uses the name. Only JIRA issues with a corresponding release will be imported. Most commonly, JIRA plug-in users will utilize the `Fix Version/s` field.~ucr-plugin-jira58
Status\ Select=Status Select~ucr-plugin-jira59
The\ JIRA\ plug-in\ can\ import\ various\ JIRA\ objects.\ Select\ JIRA\ Application,\ Release,\ Type,\ and\ Status\ mappings\ to\ define\ changes\ in\ IBM\ UrbanCode\ Release.\ Migration\ from\ the\ built-in\ plug-in\ is\ not\ supported.=The JIRA plug-in can import various JIRA objects. Select JIRA Application, Release, Type, and Status mappings to define changes in IBM UrbanCode Release. Migration from the built-in plug-in is not supported.~ucr-plugin-jira60
The\ JIRA\ server\ URL=The JIRA server URL~ucr-plugin-jira61
The\ password\ to\ use\ to\ connect\ to\ JIRA=The password to use to connect to JIRA~ucr-plugin-jira62
The\ username\ to\ use\ to\ connect\ to\ JIRA=The username to use to connect to JIRA~ucr-plugin-jira63
This\ is\ number\ of\ issue\ link\ steps\ the\ integration\ will\ make\ to\ associate\ issues\ to\ an\ initiative.\ If\ the\ depth\ is\ 2,\ the\ issue\ that\ is\ imported\ as\ an\ initiative\ will\ be\ imported\ and\ the\ children\ of\ that\ issue\ as\ well\ as\ the\ children\ of\ thos\ issues\ will\ be\ imported\ as\ changes.=This is number of issue link steps the integration will make to associate issues to an initiative. If the depth is 2, the issue that is imported as an initiative will be imported and the children of that issue as well as the children of thos issues will be imported as changes.~ucr-plugin-jira64
This\ issue\ link\ type\ is\ the\ field\ that\ will\ be\ used\ to\ determine\ the\ changes\ that\ will\ be\ associated\ to\ a\ given\ initiative=This issue link type is the field that will be used to determine the changes that will be associated to a given initiative~ucr-plugin-jira65
This\ type\ of\ issue\ will\ be\ imported\ as\ an\ initiative\ in\ UCR=This type of issue will be imported as an initiative in UCR~ucr-plugin-jira66
Type\ Select=Type Select~ucr-plugin-jira67
