Class AdministrationImpl
java.lang.Object
com.atlassian.jira.functest.framework.AdministrationImpl
- All Implemented Interfaces:
Administration
Implementation of
Administration- Since:
- v3.13
-
Nested Class Summary
Nested classes/interfaces inherited from interface com.atlassian.jira.functest.framework.Administration
Administration.Link, Administration.OutgoingMailSettings, Administration.Utilities -
Field Summary
FieldsFields inherited from interface com.atlassian.jira.functest.framework.Administration
ENTERPRISE, PROFESSIONAL, STANDARD -
Constructor Summary
ConstructorsConstructorDescriptionAdministrationImpl(net.sourceforge.jwebunit.WebTester tester, JIRAEnvironmentData environmentData, Navigation navigation, Assertions assertions) Note: if you need to construct this for an old-style, you may want to consider usinginvalid reference
com.atlassian.jira.webtests.JIRAWebTestinstead.invalid reference
com.atlassian.jira.functest.framework.FuncTestHelperFactory -
Method Summary
Modifier and TypeMethodDescriptionvoidvoidaddGlobalPermission(int permission, String group) Add a group to a Global permission Ends up on the Global Permissions page.voidaddGlobalPermission(GlobalPermissionKey permission, String group) Add a group to a Global permission Ends up on the Global Permissions page.voidaddSubTaskType(String name) Gets an instance of the AdvancedApplicationProperties Page Object.backdoor()Allows you to perform backdoor actionsvoidCopies a file to the JIRA import directory, presumably with the intention of testing imports directly.Allows you to perform custom field actions.voidenable http access loggingexportDataToFile(String fileName) Exports the current running data to the specified absolute pathAllows you to modify field configurations.Allows you to modify field configuration schemes.Allows you to perform generalConfiguration actions.longReturns ths current build number.Obtains the current attachment path configured for JIRA.Returns the current edition name.Returns the JIRA home directory as reported in the System Info sectionGet the system tenant home directory.TGo to issue linking administration section.Allows you to modify issue security schemes.link()Retrieves the administration home link in the JIRA Header.Gets an instance of the Mail Server Administration page.'Notification Schemes' administration sectionDeprecated.all new tests with the Single Page Permission Schemes page should be written in a web driver test using EditPermissionsSinglePage.plugins()Utility function to allow you some basic plugins controlproject()Allows you to perform project actions.Allows you to perform project imports.voidreIndex()Reindex JIRA, waiting for JIRA to complete the task, in the default index directory.voidremoveGlobalPermission(int permission, String group) Remove a group from a given Global Permission.voidremoveGlobalPermission(GlobalPermissionKey permissionKey, String group) Remove a group from a given Global Permission.replaceTokensInFile(String originalXmlFileName, Map<String, String> replacements) Reads in an XML file and performs token replacements on it, writes the data to a temp file which is the return valuevoidRestores a JIRA to blank instance with Data Center License.voidRestores the jira instance to one with no issues.voidrestoreBlankInstanceWithLicense(License license) Restores a JIRA to a well known blank instance with the supplied licence.voidRestores a JIRA to blank instance with Server License.voidrestoreData(String fileName) Same asAdministration.restoreData(String, boolean), but with useDefaultPaths set to false.voidrestoreData(String fileName, boolean useDefaultPaths) Restores the specified fileName as JIRA data.voidrestoreData(String fileName, Administration.OutgoingMailSettings outgoingMailSetting) voidrestoreData(String path, String fileName) voidrestoreData(String path, String fileName, boolean useDefaultPath) voidrestoreDataAndLogin(String fileName, String username) same asAdministration.restoreDataAndLogin(String, String, boolean)but with userDefaultPaths parameter set to false.voidrestoreDataAndLogin(String fileName, String username, boolean useDefaultPaths) Restore the specified file and login to JIRA using the passed username.voidrestoreDataSlowOldWay(String fileName) Same asAdministration.restoreDataSlowOldWay(String, boolean), except with useDefaultPaths set to false.voidrestoreDataSlowOldWay(String fileName, boolean useDefaultPaths) Restores the specified fileName as JIRA data NOT using the clear cache mechanism.voidrestoreDataSlowOldWay(String path, String fileName) Same asAdministration.restoreDataSlowOldWay(String, String, boolean), but with useDefaultPath set to false;voidrestoreDataSlowOldWay(String path, String fileName, boolean useDefaultPath) Restores the XML file from the specified directory NOT using the clear cache mechanism.voidrestoreDataSlowOldWayAndLogin(String fileName, String username) Same asAdministration.restoreDataSlowOldWayAndLogin(String, String, boolean)but with useDefaultPath set to false.voidrestoreDataSlowOldWayAndLogin(String fileName, String username, boolean useDefaultPath) Restore the specified file data NOT using the clear cache mechanism and login to JIRA using the passed username.voidrestoreDataWithBuildNumber(String fileName, int expectedBuilderNumber) Basically check the passed backup to ensure that it matches the passed build number and then restore the data.voidrestoreDataWithLicense(String fileName, String licenseKey) same asAdministration.restoreDataWithLicense(String, String, boolean), except with useDefaultPaths set to false.voidrestoreDataWithLicense(String fileName, String licenseKey, boolean useDefaultPaths) Restores the specified fileName as JIRA data, using the specified License key on import.voidrestoreDataWithPluginsReload(String fileName) Same asAdministration.restoreDataWithPluginsReload(String, boolean), except with useDefaultPaths set to false.voidrestoreDataWithPluginsReload(String fileName, boolean useDefaultPaths) Restores the specified fileName as JIRA data NOT using the clear cache mechanism.voidrestoreDataWithReplacedTokens(String originalXmlFileName, Map<String, String> replacements) Same asAdministration.restoreDataWithReplacedTokens(String, java.util.Map, boolean), except with useDefaultPaths set to false.voidrestoreDataWithReplacedTokens(String originalXmlFileName, Map<String, String> replacements, boolean useDefaultPaths) Reads in an XML file and performs token replacements on it, writes the data to a temp file, then imports that into JIRA.voidrestoreI18nData(String fileName) Restores the specified fileName as JIRA data.voidRestores a backup file with JIRA in an not setup state.voidrestoreNotSetupInstance(String licenseKey) Restores a backup file with JIRA in an not setup state.voidrestoreNotSetupRenaissanceInstance(String licenseKey) Deprecated.since 7.0.1, use restoreNotSetupInstanceroles()Allows you to perform role actionsGets an instance of the Send Bulk Mail Page.services()Returns the ViewServices object which allows you to run operations on the ViewServices page.voidsetProfiling(boolean on) Set JIRA's profiling on or off.Gets an instance of the Shared Filters Administration page.statuses()Gets the instance of the Statuses pagesubtasks()voidswitchToLicense(License license) Changes JIRA's lincense to a given license objectvoidswitchToLicense(String license, String description) Changes JIRA's lincense to a given license and asserts that the description then appears on the view licensevoidSwitches the license to a personal license.voidSwitches the license to a starter license.tabs()Gets an instance of the AdminTabs Page Object.Get time tracking administration section util.Allows you to perform user and group actions.Field screens config.voidWaits for the data import progress to complete.Manage the 'Workflows' administration page
-
Field Details
-
LEGACY_PROJECT_PERMISSIONS_PAGE_DARK_FEATURE
- See Also:
-
-
Constructor Details
-
Method Details
-
reIndex
public void reIndex()Description copied from interface:AdministrationReindex JIRA, waiting for JIRA to complete the task, in the default index directory.- Specified by:
reIndexin interfaceAdministration
-
setProfiling
public void setProfiling(boolean on) Description copied from interface:AdministrationSet JIRA's profiling on or off.- Specified by:
setProfilingin interfaceAdministration- Parameters:
on- or off
-
restoreBlankInstance
public void restoreBlankInstance()Restores the jira instance to one with no issues. Some projects have been created- Specified by:
restoreBlankInstancein interfaceAdministration
-
restoreBlankServerInstance
public void restoreBlankServerInstance()Description copied from interface:AdministrationRestores a JIRA to blank instance with Server License. Use this when your test relies on Server license.- Specified by:
restoreBlankServerInstancein interfaceAdministration
-
restoreBlankDataCenterInstance
public void restoreBlankDataCenterInstance()Description copied from interface:AdministrationRestores a JIRA to blank instance with Data Center License. Use this when your test relies on DC license.- Specified by:
restoreBlankDataCenterInstancein interfaceAdministration
-
restoreBlankInstanceWithLicense
Description copied from interface:AdministrationRestores a JIRA to a well known blank instance with the supplied licence.- Specified by:
restoreBlankInstanceWithLicensein interfaceAdministration- Parameters:
license- the license to be installed
-
restoreNotSetupInstance
public void restoreNotSetupInstance()Description copied from interface:AdministrationRestores a backup file with JIRA in an not setup state. If you use this method, you will have to then set up JIRA from scratch!- Specified by:
restoreNotSetupInstancein interfaceAdministration
-
restoreNotSetupInstance
Description copied from interface:AdministrationRestores a backup file with JIRA in an not setup state. If you use this method, you will have to then set up JIRA from scratch!- Specified by:
restoreNotSetupInstancein interfaceAdministration- Parameters:
licenseKey- the license key to be used for restore
-
restoreNotSetupRenaissanceInstance
Deprecated.since 7.0.1, use restoreNotSetupInstanceThis can be removed after JIRA renaissance has been released (7.0) as roles would be enabled by default. Tracked in HIROL-1075- Specified by:
restoreNotSetupRenaissanceInstancein interfaceAdministration- Parameters:
licenseKey- the license key to be used for restore
-
copyFileToJiraImportDirectory
Description copied from interface:AdministrationCopies a file to the JIRA import directory, presumably with the intention of testing imports directly.- Specified by:
copyFileToJiraImportDirectoryin interfaceAdministration- Parameters:
file- the file to copy to JIRA_HOME/import
-
replaceTokensInFile
public File replaceTokensInFile(String originalXmlFileName, Map<String, String> replacements) throws IOExceptionDescription copied from interface:AdministrationReads in an XML file and performs token replacements on it, writes the data to a temp file which is the return value- Specified by:
replaceTokensInFilein interfaceAdministration- Parameters:
originalXmlFileName- the name of the XML file to read in; must be located in the standard XML file directoryreplacements- a map of token replacements- Returns:
- a new temporary file that has its tokens replaced
- Throws:
IOException- if there is a problem reading/writing the files
-
restoreDataWithReplacedTokens
public void restoreDataWithReplacedTokens(String originalXmlFileName, Map<String, String> replacements) throws IOExceptionDescription copied from interface:AdministrationSame asAdministration.restoreDataWithReplacedTokens(String, java.util.Map, boolean), except with useDefaultPaths set to false.- Specified by:
restoreDataWithReplacedTokensin interfaceAdministration- Throws:
IOException
-
restoreDataWithReplacedTokens
public void restoreDataWithReplacedTokens(String originalXmlFileName, Map<String, String> replacements, boolean useDefaultPaths) throws IOExceptionDescription copied from interface:AdministrationReads in an XML file and performs token replacements on it, writes the data to a temp file, then imports that into JIRA. Note: this only works when the FuncTest client is running on the same host as the JIRA server. For methods to create date strings to use as your tokens, check out theDateUtilclass- Specified by:
restoreDataWithReplacedTokensin interfaceAdministration- Parameters:
originalXmlFileName- the name of the XML file to read in; must be located in the standard XML file directoryreplacements- a map of token replacementsuseDefaultPaths- if set to true, the paths (e.g., attachment, index) in the xml backup will be ignored, and the default used instead. If the token being replaced is part of the default paths, it is still replaced prior to restore.- Throws:
IOException- if there is a problem reading/writing the files
-
restoreData
Description copied from interface:AdministrationSame asAdministration.restoreData(String, boolean), but with useDefaultPaths set to false.- Specified by:
restoreDatain interfaceAdministration
-
restoreData
Description copied from interface:AdministrationRestores the specified fileName as JIRA data.- Specified by:
restoreDatain interfaceAdministration- Parameters:
fileName- the XML file inside the standard backup file directory containing the JIRA datauseDefaultPaths- if set to true, the xml backup's paths (e.g., index, attachment etc) will be ignored, and the default for those used in stead
-
restoreData
- Specified by:
restoreDatain interfaceAdministration
-
link
Description copied from interface:AdministrationRetrieves the administration home link in the JIRA Header.- Specified by:
linkin interfaceAdministration- Returns:
- the administration home link in the JIRA Header.
-
restoreDataAndLogin
Description copied from interface:Administrationsame asAdministration.restoreDataAndLogin(String, String, boolean)but with userDefaultPaths parameter set to false.- Specified by:
restoreDataAndLoginin interfaceAdministration
-
restoreDataAndLogin
Description copied from interface:AdministrationRestore the specified file and login to JIRA using the passed username.- Specified by:
restoreDataAndLoginin interfaceAdministration- Parameters:
fileName- the name of the xml file to restore.username- the username used to login to JIRA after the restore. The username and the password are assumed to be the same.useDefaultPaths- if set to true, the xml backup's paths (e.g., index, attachment etc) will be ignored, and the default for those used in stead
-
restoreDataSlowOldWayAndLogin
Description copied from interface:AdministrationSame asAdministration.restoreDataSlowOldWayAndLogin(String, String, boolean)but with useDefaultPath set to false.- Specified by:
restoreDataSlowOldWayAndLoginin interfaceAdministration
-
restoreDataSlowOldWayAndLogin
Description copied from interface:AdministrationRestore the specified file data NOT using the clear cache mechanism and login to JIRA using the passed username. This is much slower than using the default methods and should only be used if there is a real reason for it. If you find yourself using this method perhaps we should be fixing the cache clearing stuff instead.- Specified by:
restoreDataSlowOldWayAndLoginin interfaceAdministration- Parameters:
fileName- the name of the xml file to restore.username- the username used to login to JIRA after the restore. The username and the password are assumed to be the same.useDefaultPath- if set to true, the paths in the xml backup (e.g., index, and attachment) will be ignored, and their default paths used instead.
-
restoreDataSlowOldWay
Description copied from interface:AdministrationSame asAdministration.restoreDataSlowOldWay(String, boolean), except with useDefaultPaths set to false.- Specified by:
restoreDataSlowOldWayin interfaceAdministration
-
restoreDataSlowOldWay
Description copied from interface:AdministrationRestores the specified fileName as JIRA data NOT using the clear cache mechanism. This is much slower than using the default methods and should only be used if there is a real reason for it. If you find yourself using this method perhaps we should be fixing the cache clearing stuff instead.- Specified by:
restoreDataSlowOldWayin interfaceAdministration- Parameters:
fileName- the XML file inside the standard backup file directory containing the JIRA datauseDefaultPaths- if set to true, the paths in the xml backup (e.g., index, and attachment) will be ignored, and their default paths used instead.
-
restoreDataWithPluginsReload
Description copied from interface:AdministrationSame asAdministration.restoreDataWithPluginsReload(String, boolean), except with useDefaultPaths set to false.- Specified by:
restoreDataWithPluginsReloadin interfaceAdministration
-
restoreDataWithPluginsReload
Description copied from interface:AdministrationRestores the specified fileName as JIRA data NOT using the clear cache mechanism. The plugins system is restarted.
This restore uses the full Pico refresh the same as in Production. ie it does not do a "Quick Import".
This is much slower than using the default methods and should only be used if there is a real reason for it.
- Specified by:
restoreDataWithPluginsReloadin interfaceAdministration- Parameters:
fileName- the XML file inside the standard backup file directory containing the JIRA datauseDefaultPaths- if set to true, the paths in the xml backup (e.g., index, and attachment) will be ignored, and their default paths used instead.
-
restoreData
-
restoreData
-
restoreDataSlowOldWay
Description copied from interface:AdministrationSame asAdministration.restoreDataSlowOldWay(String, String, boolean), but with useDefaultPath set to false;- Specified by:
restoreDataSlowOldWayin interfaceAdministration
-
restoreDataSlowOldWay
Description copied from interface:AdministrationRestores the XML file from the specified directory NOT using the clear cache mechanism. This is much slower than using the default methods and should only be used if there is a real reason for it. If you find yourself using this method perhaps we should be fixing the cache clearing stuff instead.- Specified by:
restoreDataSlowOldWayin interfaceAdministration- Parameters:
path- the directory in which the XML file is locatedfileName- the name of the XML fileuseDefaultPath- if set to true, the paths (e.g., attachment, index) in the xml backup will be ignored, and the default used instead
-
restoreDataWithLicense
Description copied from interface:AdministrationRestores the specified fileName as JIRA data, using the specified License key on import.- Specified by:
restoreDataWithLicensein interfaceAdministration- Parameters:
fileName- the file conatining the JIRA datalicenseKey- the license key to be installeduseDefaultPaths- if set to true, the paths (e.g., attachment, index) in the xml backup will be ignored, and the default used instead
-
restoreDataWithLicense
Description copied from interface:Administrationsame asAdministration.restoreDataWithLicense(String, String, boolean), except with useDefaultPaths set to false.- Specified by:
restoreDataWithLicensein interfaceAdministration
-
restoreI18nData
Description copied from interface:AdministrationRestores the specified fileName as JIRA data. Does not make english assertions.- Specified by:
restoreI18nDatain interfaceAdministration- Parameters:
fileName- the fiel conatining the JIRA data
-
restoreDataWithBuildNumber
Description copied from interface:AdministrationBasically check the passed backup to ensure that it matches the passed build number and then restore the data. An exception will be thrown if the backup does not match the passed build number.- Specified by:
restoreDataWithBuildNumberin interfaceAdministration- Parameters:
fileName- the path of the backup.expectedBuilderNumber- the build number the data should have.
-
exportDataToFile
Description copied from interface:AdministrationExports the current running data to the specified absolute path- Specified by:
exportDataToFilein interfaceAdministration- Parameters:
fileName- to backup to. This should just be a filename because JIRA always appends ${JIRA.HOME}/export to it before doing the export. Passing a directory may make it fail on windows.- Returns:
- export file. it will be absolute.
-
getCurrentAttachmentPath
Description copied from interface:AdministrationObtains the current attachment path configured for JIRA. This method does not check whether Attachments are enabled or not. If JIRA is configured to use the "default" attachment path, then this method still returns the ACTUAL path that is used. The implementation navigates to the Admin Attachments Settings page and screenscrapes, so don't expect to remain on the same page as when you called the method.- Specified by:
getCurrentAttachmentPathin interfaceAdministration- Returns:
- the current attachment path configured for JIRA.
-
activateSubTasks
public void activateSubTasks()- Specified by:
activateSubTasksin interfaceAdministration
-
addSubTaskType
- Specified by:
addSubTaskTypein interfaceAdministration
-
generalConfiguration
Description copied from interface:AdministrationAllows you to perform generalConfiguration actions.- Specified by:
generalConfigurationin interfaceAdministration- Returns:
- generalConfiguration
-
backdoor
Description copied from interface:AdministrationAllows you to perform backdoor actions- Specified by:
backdoorin interfaceAdministration- Returns:
- backdoor
-
project
Description copied from interface:AdministrationAllows you to perform project actions.- Specified by:
projectin interfaceAdministration- Returns:
- project
-
usersAndGroups
Description copied from interface:AdministrationAllows you to perform user and group actions.- Specified by:
usersAndGroupsin interfaceAdministration- Returns:
- usersAndGroups
-
roles
Description copied from interface:AdministrationAllows you to perform role actions- Specified by:
rolesin interfaceAdministration- Returns:
- roles
-
customFields
Description copied from interface:AdministrationAllows you to perform custom field actions.- Specified by:
customFieldsin interfaceAdministration- Returns:
- customFields
-
permissionSchemes
Deprecated.all new tests with the Single Page Permission Schemes page should be written in a web driver test using EditPermissionsSinglePage. For backdoor based PermissionSchemes control useBackdoor.permissionSchemes()Description copied from interface:AdministrationAllows you to modify permission schemes.- Specified by:
permissionSchemesin interfaceAdministration- Returns:
- permissionSchemes
-
issueSecuritySchemes
Description copied from interface:AdministrationAllows you to modify issue security schemes.- Specified by:
issueSecuritySchemesin interfaceAdministration- Returns:
- issue security schemes of this administration
-
fieldConfigurations
Description copied from interface:AdministrationAllows you to modify field configurations.- Specified by:
fieldConfigurationsin interfaceAdministration- Returns:
- fieldConfigurations
-
fieldConfigurationSchemes
Description copied from interface:AdministrationAllows you to modify field configuration schemes.- Specified by:
fieldConfigurationSchemesin interfaceAdministration- Returns:
- fieldConfigurationSchemes
-
projectImport
Description copied from interface:AdministrationAllows you to perform project imports.- Specified by:
projectImportin interfaceAdministration- Returns:
- projectImport
-
plugins
Description copied from interface:AdministrationUtility function to allow you some basic plugins control- Specified by:
pluginsin interfaceAdministration- Returns:
- plugins
-
removeGlobalPermission
Description copied from interface:AdministrationRemove a group from a given Global Permission. Ends up on the Global Permissions page.- Specified by:
removeGlobalPermissionin interfaceAdministration- Parameters:
permissionKey- The permission to remove the group fromgroup- the group to remove
-
removeGlobalPermission
Description copied from interface:AdministrationRemove a group from a given Global Permission. Ends up on the Global Permissions page.- Specified by:
removeGlobalPermissionin interfaceAdministration- Parameters:
permission- The permission to remove teh group fromgroup- the group to remove
-
addGlobalPermission
Description copied from interface:AdministrationAdd a group to a Global permission Ends up on the Global Permissions page.- Specified by:
addGlobalPermissionin interfaceAdministration- Parameters:
permission- the permission to add the group togroup- The group to add
-
addGlobalPermission
Description copied from interface:AdministrationAdd a group to a Global permission Ends up on the Global Permissions page.- Specified by:
addGlobalPermissionin interfaceAdministration- Parameters:
permission- the permission to add the group togroup- The group to add
-
switchToLicense
Description copied from interface:AdministrationChanges JIRA's lincense to a given license object- Specified by:
switchToLicensein interfaceAdministration- Parameters:
license- license to switch to
-
switchToLicense
Description copied from interface:AdministrationChanges JIRA's lincense to a given license and asserts that the description then appears on the view license- Specified by:
switchToLicensein interfaceAdministration- Parameters:
license- license to switch todescription- license description
-
switchToPersonalLicense
public void switchToPersonalLicense()Description copied from interface:AdministrationSwitches the license to a personal license.- Specified by:
switchToPersonalLicensein interfaceAdministration
-
switchToStarterLicense
public void switchToStarterLicense()Description copied from interface:AdministrationSwitches the license to a starter license.- Specified by:
switchToStarterLicensein interfaceAdministration
-
getJiraHomeDirectory
Description copied from interface:AdministrationReturns the JIRA home directory as reported in the System Info section- Specified by:
getJiraHomeDirectoryin interfaceAdministration- Returns:
- the JIRA home directory as reported in the System Info section
-
getSystemTenantHomeDirectory
Description copied from interface:AdministrationGet the system tenant home directory. This does the same thing as getJiraHomeDirectory, except it doesn't cache it in a thread local. It assumes that the environment data for this administration object is for the system tenant. It should only be called when a tenant is provisioned, which should only be done on the first test to that tenant.- Specified by:
getSystemTenantHomeDirectoryin interfaceAdministration- Returns:
- The system tenant home directory.
-
mailServers
Description copied from interface:AdministrationGets an instance of the Mail Server Administration page.- Specified by:
mailServersin interfaceAdministration- Returns:
- an instance of the Mail Server Administration page.
-
sendBulkMail
Description copied from interface:AdministrationGets an instance of the Send Bulk Mail Page.- Specified by:
sendBulkMailin interfaceAdministration- Returns:
- an instance of the Send Bulk Mail Page.
-
tabs
Description copied from interface:AdministrationGets an instance of the AdminTabs Page Object.- Specified by:
tabsin interfaceAdministration- Returns:
- an instance of the AdminTabs Page Object.
-
advancedApplicationProperties
Description copied from interface:AdministrationGets an instance of the AdvancedApplicationProperties Page Object.- Specified by:
advancedApplicationPropertiesin interfaceAdministration- Returns:
- an instance of the AdvancedApplicationProperties Page Object.
-
statuses
Description copied from interface:AdministrationGets the instance of the Statuses page- Specified by:
statusesin interfaceAdministration
-
subtasks
- Specified by:
subtasksin interfaceAdministration- Returns:
- grouping to manage administration of subtasks
-
issueLinking
Description copied from interface:AdministrationTGo to issue linking administration section.- Specified by:
issueLinkingin interfaceAdministration- Returns:
- grouping to manage issue linking
-
timeTracking
Description copied from interface:AdministrationGet time tracking administration section util.- Specified by:
timeTrackingin interfaceAdministration- Returns:
- time tracking configuration
-
resolutions
- Specified by:
resolutionsin interfaceAdministration- Returns:
- resolution configuration
-
services
Description copied from interface:AdministrationReturns the ViewServices object which allows you to run operations on the ViewServices page.- Specified by:
servicesin interfaceAdministration- Returns:
- the ViewServices object which allows you to run operations on the ViewServices page.
-
getEdition
Description copied from interface:AdministrationReturns the current edition name. This may be useful for licensing checks- Specified by:
getEditionin interfaceAdministration- Returns:
- the current edition name
- See Also:
-
getBuildNumber
public long getBuildNumber()Description copied from interface:AdministrationReturns ths current build number. ARuntimeExceptionwill be thrown if we can't find the build number.- Specified by:
getBuildNumberin interfaceAdministration- Returns:
- JIRA's build number.
-
enableAccessLogging
public void enableAccessLogging()Description copied from interface:Administrationenable http access logging- Specified by:
enableAccessLoggingin interfaceAdministration
-
attachments
- Specified by:
attachmentsin interfaceAdministration- Returns:
- attachments
-
viewFieldScreens
Description copied from interface:AdministrationField screens config.- Specified by:
viewFieldScreensin interfaceAdministration- Returns:
- field screens config
-
utilities
- Specified by:
utilitiesin interfaceAdministration- Returns:
- utilities
-
workflows
Description copied from interface:AdministrationManage the 'Workflows' administration page- Specified by:
workflowsin interfaceAdministration- Returns:
ViewWorkflowsinstance
-
notificationSchemes
Description copied from interface:Administration'Notification Schemes' administration section- Specified by:
notificationSchemesin interfaceAdministration- Returns:
NotificationSchemesinstance
-
waitForRestore
public void waitForRestore()Description copied from interface:AdministrationWaits for the data import progress to complete.- Specified by:
waitForRestorein interfaceAdministration
-