Deprecated API
Contents
-
Terminally Deprecated Elements
-
Deprecated InterfacesInterfaceDescriptionsince v8.12
UseAuditResourceinstead.since v8.8
UseAuditServiceandAuditSearchServiceinstead.since v8.12
UseAuditServiceandAuditSearchServiceinstead.since v8.12
UseAuditEntityinstead.since v8.12
UseChangedValueinstead.since v8.12Avatar URLs returned by AvatarService are URI References, removing the need for absolute/relative schismUseUserSearchServiceinstead. Since v7.0.UseQueryDslAccessorall 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()since JIRA 6.2. Since the replacement of the issue navigator by KickAss, the use of this class is unpredictable.Since 8.21. UseIssueFinderV2insteadPlease useSortableCustomFieldSearcherinstead.Use Lucene Doc Values. Since v8.0. SeeReaderCachefor more information.Use Lucene Doc Values. Since v8.0. Before Jira v8.0ReaderCacheused to create a cache ofJiraDocValuesfrom Lucene index. Since Jira v8.0ReaderCacheis using LuceneDocValues.UseTemporaryWebAttachmentManagerinstead. Since v6.4Use the Data object getters instead. Since v5.0.Since v7.1. This feature is deprecated and will not be supported in production in cloud as of October 2015 as it maked the content of resources unpredictable thus causing caching and pre-baking issues. It is a runtime error to have a<translation-transformation>in any plugin in production in cloud.please useUserFormatsinstead.This is plugin module is slated for removal. https://developer.atlassian.com/x/dsfgAQ details how to integrate with the new project centric view in JIRA going forward. Since 7.0.This is plugin module is slated for removal. https://developer.atlassian.com/x/dsfgAQ details how to integrate with the new project centric view in JIRA going forward. Since 7.0.since v6.3 - useWebItemProviderModuleDescriptorsince v6.3 - useWebItemProvidersince 6.3 - useDynamicWebInterfaceManagerdirectly.since v6.3 - useDynamicWebInterfaceManagerdirectly if possible.v6.2 This is no longer used.UseClockinsteadsince v4.0 use theConcurrentOperationMapdirectly.since 7.1 Storing information on theHttpSessionis not supported. Please move the functionality to the frontend or other type of storage. This class will be removed in 8.0.UseIssueServiceinstead (will be moved into jira-core). Since v6.2.Since 7.1. Storing this on the httpSession does not work for cloud. Storing information on the httpsession is obsoleted. Please move this functionality to the frontend or other type of storage. This class will be removed in 8.0.since 7.1 Storing information on the httpsession is obsoleted. Please move this functionality to the frontend or other type of storage. This method will be removed in 8.0.UseIssueServiceorIssueManagerinstead. Since v5.0.since 7.1 Storing information in server side HttpSession is not Vertigo alignedsince 7.1 Storing information on the httpsession is obsoleted. Please move this functionality to the frontend or other type of storage. This class will be removed in 8.0.since 7.1 Storing information on the httpsession is obsoleted. Please move this functionality to the frontend or other type of storage. This class will be removed in 8.0.since 7.1 Storing information on the httpsession is obsoleted. Please move this functionality to the frontend or other type of storage. This method will be removed in 8.0.since 7.1 Storing information on the httpsession is obsoleted. Please move this functionality to the frontend or other type of storage. This method will be removed in 8.0.since 7.1 Storing information on the httpsession is obsoleted. Please move this functionality to the frontend or other type of storage. This method will be removed in 8.0.since 7.1 Storing information on the httpsession is obsoleted. Please move this functionality to the frontend or other type of storage. This method will be removed in 8.0.since 7.1 Storing information on theHttpSessionis not supported. Please move the functionality to the frontend or other type of storage.Use JIRA.Templates.ViewIssue.matchFileIconUrl or JIRA.Templates.ViewIssue.matchFileIconAlt soy template instead.UseDateTimeFormatterFactory.formatter()instead. Since v4.4.UseTemporaryWebAttachmentManagerinstead. Since v6.4.
-
Deprecated ClassesClassDescriptionUse
EntityUtilsinstead. Since v5.1.since v8.12
UseAuditQueryinstead.useAuditServiceinsteadsince v8.12
UseAuditEventinsteadThis class does not work universally. UseIconImageResolverImpl. Since v7.1This is not needed. UseIconImageResolverImpl. Since v7.1This is not needed. UseIconImageResolverImpl. Since v7.1since 9.13 as it always returns true for isDC and there's nothing else in this moduleNo replacement needed. Since v7.0 (but pointless since v4.3 or so).since 9.13 as it always returns true for isDCThis is not used in Jira ServerThis is not used in Jira ServerThis is not used in Jira ServerThis is not used in Jira ServerSince v5.0 useIssueEventManagerinstead.UseJiraUpgradeFinishedEventinstead. Since v7.4.UseProjectPermissions.CREATE_ISSUESorProjectPermissions.EDIT_ISSUESinstead.all new tests with the Single Page Permission Schemes page should be written in a web driver test using EditPermissionsSinglePage.since JIRA 6.2. Since the replacement of the issue navigator by KickAss, the use of this class is unpredictable.Do not use, this is internal class and will be removedDo not use, this is internal class and will be removedsince v6.2 This class is redundant, and not used by JIRA.since 4.0. use ProjectComponent instead of GenericValue and compare throughProjectComponentComparatorThis class is unnecessary. Since v6.4.Implement the methods onMultipleSettableCustomFieldTypeyourself. Since v5.0. Also, consider extendingAbstractSingleFieldTypeorAbstractMultiCFTypefor other benefitsUseGenericTextCFTypeinstead. Since v5.0.UseGenericTextCFTypeinstead. Since v5.0.UseTemporaryWebAttachmentManagerinstead. Since v6.4Use Lucene Doc Values directly. Since v8.0.UseCachingBytesRefMapperinstead. Since v7.5.useMockitoJUnit.rule()insteaduseMockJiraWorkflow, or Mockito mocks in your tests. Unless you really really think you need to load your workflow from XML file. In which case still use the above alternatives.since 6.2. UseBasicSearchinstead.since 7.1.0 - useEditPermissionsSinglePage.GrantPermissionsDialoginsteadsince 7.1.0 - useEditPermissionsSinglePagedirectly insteadsince 7.4. Remove with 8.0since 7.1.0 - useEditPermissionsSinglePage.RevokePermissionsDialoginsteadsince 7.1.0 - useEditPermissionsSinglePageinsteaduseEditPermissionsSinglePage.PermissionsEntryinsteaduseinsteadas there is no longer this header in project config because of the new sidebar.Please extendAbstractProjectTabPanelinstead. Since v5.0.ExtendAbstractProjectTabPanelinstead. Since v5.0.Substituted byDefaultUserFormatsExtendAbstractIssueWebConditioninstead. Since v6.0.ExtendAbstractWebConditioninstead. Since v6.0.since 6.3 - useDynamicWebInterfaceManagerdirectlysince v6.3 - useDynamicWebInterfaceManagerdirectly if possible.This class is inherently unsafe to use in a clustered environment. UseCachingOfBizPropertySet(keyed as"ofbiz-cached"instead. Since v6.2.Do not add new entries here, useComponentImportannotations on the consuming class' constructor parameters instead.This class is deprecated and will be deleted in Jira 10.Superseded byErrorCollectionSuperseded byErrorCollectionUseAvatarUrlsif you really must. Since v6.1.THIS IS A COPY OFFieldBean. This class is deprecated and will be removed with 7.0.use theMockI18nHelper(in the right package),NoopI18nHelper, or Mockito mocks insteadUse fields and utility methods defined inProjectPermissionsandGlobalPermissionKey. Since v6.3.Use MailFetcherService directlyUse MailFetcherService directlysince 7.1 Storing information on theHttpSessionis not supported. Please move the functionality to the frontend or other type of storage. This class will be removed in 8.0.you shouldn't be using this class directly, useBuildUtilsInfoinstead.UseClockinsteadsince 10.0, use Java built-in utilities or specialised librariessince 10.0, use Java built-in utilities or specialised librariesUseClockinsteadsince v4.0 useConcurrentOperationMapImpldirectlySwitch toLazyReferenceinstead.UseClockinsteadUseListsinstead. Since v5.0.UseClockinsteadUse Guava or build your own inverter instead. Since v6.3.Use API methods that don't require GenericValues instead, or copy/paste these methods as we intend to pull this out of the API. Since v6.1.UseClockinsteadUseClockinsteadUseClockinsteadsince 7.1 Storing information on theHttpSessionis not supported. Please move the functionality to the frontend or other type of storage. This class will be removed in 8.0.useWorkflowTransitionContextUtilsinstead. Since 7.1.Since v5.0.UseTemporaryWebAttachmentManagerinstead. Since v6.4UseRedirectSanitiserinstead. Since v6.2.Since 7.1. Storing information on the httpsession is obsoleted. Please move this functionality to the frontend or other type of storage.since 7.1 Storing information on the httpsession is obsoleted. Please move this functionality to the frontend or other type of storage. This class will be removed in 8.0.since 7.1 Storing information in server side HttpSession is not Vertigo alignedsince 7.1 Storing information on the httpsession is obsoleted. Please move this functionality to the frontend or other type of storage. This class will be removed in 8.0.since 7.1 Storing information on the httpsession is obsoleted. Please move this functionality to the frontend or other type of storage. This class will be removed in 8.0.since 7.1 Storing information on the httpsession is obsoleted. Please move this functionality to the frontend or other type of storage. This class will be removed in 8.0.since 7.1 Storing information on the httpsession is obsoleted. Please move this functionality to the frontend or other type of storage. This class will be removed in 8.0.since 7.1 Storing information on the httpsession is obsoleted. Please move this functionality to the frontend or other type of storage. This class will be removed in 8.0.Use JIRA.Templates.ViewIssue.matchFileIconUrl or JIRA.Templates.ViewIssue.matchFileIconAlt soy template instead.Use JIRA.Templates.ViewIssue.matchFileIconUrl or JIRA.Templates.ViewIssue.matchFileIconAlt soy template instead.since v6.2.4: The use of this class is discouraged. It now suggested to:-
Use an injected
HelpUrlswhen you would have calledHelpUtil.getInstance()orHelpUtil(). It contains all of JIRA's help URLs and will adapt itself internally for the current user. -
Use an injected
HelpUrlsParserwhen you would have calledHelpUtil(java.util.Properties).HelpUrlsParser.parse(java.util.Properties)can be used to generate to generate aHelpUrlsfrom a plugin providedPropertiesinstance.
This information is all available in the Issue object and this object is not actually used anywhere in core JIRA. Since v6.3.Should use theLocaleManagerinterface orLocaleParserinstead.UseDateTimeFormatterinstead. Since v7.1since 7.3.moved toBaseJiraWebTestuseSystemPropertyBasedSuiteinsteadThis class is here for legacy reasons - it may be contained in other people'ssince 3.5.2 usePermissionValidatorinstead. Note this cannot be removed without an upgrade task for existing users. -
Use an injected
-
Deprecated Enum ClassesEnum ClassDescriptionsince v8.12
Instead you can useAuditCategory.UseIconTypein place of this. Since v7.1in JIRA 6.0 -- useAvatar.Size.useIssueOperationinsteadUseDateTimeFormatterinstead. Since v5.0.
-
Deprecated ExceptionsExceptionsDescriptionPlease use
DataAccessExceptioninstead.Only used in deprecated method. Since v5.2.
-
Deprecated FieldsFieldDescriptionuse
AuditRecordImpl.LONG_DESCRIPTIONinstead. Since 7.0.0.use getMaximumKeyLength() insteaduse getMaximumNameLength() instead;since 8.20, use LIMITED_ACTIVE_USERS_ALLOW_EMPTY_QUERY insteadsince 8.20, use LIMITED_ACTIVE_USERS_IGNORE_EMPTY_QUERY insteadThis property is ignored since Jira 8.14.0. and can be removed in Jira 9.0com.atlassian.jira.component.pico.registrar.CacheManagerRegistrar.DISABLE_DEFERRED_CACHE_REPLICATIONThis property is ignored since Jira 8.14.0. and can be removed in Jira 9.0since Jira 6.1.1since 7.0.0. Jira no longer uses this property so no replacement will be provided.no longer used as of Jira 6.1. Will be removed in Jira 7.0.since 7.0. SeeJiraLicenseManager.getLicenses()since 6.2since 6.2since 6.3.3 Jira needs indexing and it cannot be disabled. SeeIndexLifecycleManager.isIndexAvailable()since Jira 6.3. UseGravatarSettingsinstead.since 7.1.1no longer used as of Jira 6.1. Will be removed in Jira 7.0.no longer used as of Jira 6.1. Will be removed in Jira 7.0.since 8.15, use $UiSettingsStateManager.getStateHash()since Jira 8.5. useLookAndFeelBean.DefaultColours.HERO_BUTTON_BASEBGCOLOURdirectly.since Jira 8.5. useLookAndFeelBean.DefaultColours.HERO_BUTTON_TXTCOLOURdirectly.since Jira 6.0. useLookAndFeelBean.DefaultColours.TOP_BGCOLOURdirectly.since Jira 6.0. useLookAndFeelBean.DefaultColours.TOP_HIGHLIGHTCOLOURdirectly.since Jira 6.0. useLookAndFeelBean.DefaultColours.TOP_SEPARATOR_BGCOLOURdirectly.This is no longer used. Since v6.4.6.since v6.1since 7.0.1since 7.0.1since v6.2.3 useCustomFieldUtils.getParamKeyRequireProjectIds()instead.useAbstractIssueNavigatorPage.searchButtoninstead.useAbstractIssueNavigatorPage.searchButtoninstead.UseApplicationAuthorizationServiceinstead.Since v7.0.UseGlobalPermissionKey.ADMINISTERinstead. This was never public API. Since v6.2.5.UseGlobalPermissionKey.BULK_CHANGEinstead. This was never public API. Since v6.2.5.UseGlobalPermissionKey.CREATE_SHARED_OBJECTSinstead. This was never public API. Since v6.2.5.UseGlobalPermissionKey.GLOBAL_PERMISSION_ID_TRANSLATIONinstead. This was never public API. Since v6.2.5.UseGlobalPermissionKey.MANAGE_GROUP_FILTER_SUBSCRIPTIONSinstead. This was never public API. Since v6.2.5.UseGlobalPermissionKey.SYSTEM_ADMINinstead. This was never public API. Since v6.2.5.UseGlobalPermissionKey.USEinstead. This was never public API. Since v6.2.5.UseGlobalPermissionKey.USER_PICKERinstead. This was never public API. Since v6.2.5.useSearchRequestURLHandler.Parameter.NO_HEADERSinstead. Deprecated in v3.13Do not use MAX_PERMISSION - it is unsafe due to the way that Java compiles constant ints, and no longer relevant. Since v6.2.3UseApplicationAuthorizationServiceinstead.Since v7.0.since 6.0 - useJiraWebActionSupport.getHttpRequest()instead.useFieldRenderingContext.EXCEL_VIEWinsteaduseFieldRenderingContext.NAVIGATOR_VIEWinsteadsince v7.1.0 this is no longer in use and will be deleted next time we break API compatibility (v8.0.0)useSessionKeys.TEMP_WEB_ATTACHMENTSinstead.since v7.1 use theUserIssueTypeManagersince v7.1 use theUserIssueTypeManagerUseJiraWorkflow.JIRA_META_UPDATE_AUTHOR_KEYinstead. Since v6.0.
-
Deprecated MethodsMethodDescriptionUse
OfBizDelegatoror getDelegatorInterfacefrom Pico instead. Since v5.0.Since v7.5.0. Please only useTxn.begin()orTransactionSupportdirectly for your managed transactionsSince v7.5.0. Please only useTxn.begin()orTransactionSupportdirectly for your managed transactionsSince v7.5.0. Please only useTxn.begin()orTransactionSupportdirectly for your managed transactionsSince v7.5.0. Please only useTxn.begin()orTransactionSupportdirectly for your managed transactionsNot used in JIRA code - please replicate this if you want to use it. Since v5.1.UseEntityUtils.createValue(String, java.util.Map)instead. Since v5.1.UseEntityUtil.filterByAnd(java.util.List, java.util.List)instead or write your own filter. Since v5.1.UseEntityUtils.getNextStringId(String)instead. Since v5.1.Not used in JIRA code - please replicate this if you want to use it. Since v5.1.UseEntityUtils.identical(org.ofbiz.core.entity.GenericValue, org.ofbiz.core.entity.GenericValue)instead. Since v5.1.since 7.0.1 as this always returns true in JIRA 7since v8.12.2
Instead useAuditEntitiesUtils.newAuditType(CoverageArea, String, String, CoverageLevel).UseAuditServiceinsteadsince 7.0.0. UseAuditingService.storeRecord(String, String, AssociatedItem, Iterable, Iterable, String)insteadsince 7.0.0. UseAuditingService.storeRecord(String, String, String, AssociatedItem, Iterable, Iterable, String)insteadUseRecords.getResults()instead. Since v6.3.4.UseAvatar.getIconType()instead. Since v7.1UseAvatarManager.getAllSystemAvatars(IconType)instead. Since v7.1there can only be one. Since v6.4.UseAvatarManager.getDefaultAvatarId(IconType)Since v7.1UseAvatarManager.userCanView(ApplicationUser, Avatar)Since v6.0UseAvatarManager.userCanView(ApplicationUser, Avatar)Since v7.1UseAvatarManager.userCanView(ApplicationUser, Avatar)Since v7.1To be removed. Since v6.0v7.0.1 Please useAvatarManager.readAvatarData(Avatar, Avatar.Size, Consumer)UseAvatarService.getAvatar(ApplicationUser, ApplicationUser). Since v6.0UseAvatarService.getAvatarURL(ApplicationUser, ApplicationUser). Since v6.0UseAvatarService.getAvatarUrlNoPermCheck(ApplicationUser, Size). Since v6.0this is an avatar-provider plugin-implementation-specific concernthe notion of "all the avatar sizes" is broken. We plan to eventually scale to any reasonable pixel size.This method cannot understand pluggable icon types. UseTemporaryAvatars.storeTemporaryAvatar(ApplicationUser, TemporaryAvatar, IconType, IconOwningObjectId). Since v7.1This interface only supportsAvatar.Type.PROJECTandAvatar.Type.ISSUETYPE. It is better to callAvatarManagerdirectly than to use TypeAvatarService.This interface only supportsAvatar.Type.PROJECTandAvatar.Type.ISSUETYPE. It is better to callAvatarManagerdirectly than to use TypeAvatarService.this option does nothing. To be removed in 7.0.UseCommentService.getCommentsForUser(ApplicationUser currentUser, Issue issue)instead. Since v6.3.use this object instead of the stinky GenericValue!use this object insteaddon't use GenericValue use the ProjectComponent instead.don't use GenericValue use the ProjectComponent instead.use findComponentsByIssue that returns a Collectioninstead since 6.3, use#create(com.atlassian.crowd.embedded.api.User, com.atlassian.jira.util.ErrorCollection, String, String, String, Long, Long)insteadUseProjectService.AbstractProjectValidationResult.getLeadUsername()instead. Since v6.0.UseProjectService.getAllProjectsForAction(ApplicationUser, ProjectAction)instead. Since v7.10.useProjectService.validateUpdateProject(ApplicationUser, UpdateProjectRequest)instead; since v7.2useProjectService.validateUpdateProject(ApplicationUser, UpdateProjectRequest)instead; since v7.2useProjectService.validateUpdateProject(ApplicationUser, UpdateProjectRequest)instead; since v7.2useProjectService.validateUpdateProject(ApplicationUser, UpdateProjectRequest)instead; since v7.2useProjectService.validateUpdateProject(ApplicationUser, UpdateProjectRequest)instead; since v7.2useProjectService.validateUpdateProject(ApplicationUser, UpdateProjectRequest)instead; since v7.2useProjectService.validateUpdateProject(ApplicationUser, UpdateProjectRequest)instead; since v7.2UseVersionService.validateCreate(com.atlassian.jira.user.ApplicationUser, com.atlassian.jira.bc.project.version.VersionService.VersionBuilder)andVersionService.create(com.atlassian.jira.user.ApplicationUser, com.atlassian.jira.bc.project.version.VersionService.VersionBuilderValidationResult). Since v6.4UseVersionService.validateCreate(com.atlassian.jira.user.ApplicationUser, com.atlassian.jira.bc.project.version.VersionService.VersionBuilder)andVersionService.create(com.atlassian.jira.user.ApplicationUser, com.atlassian.jira.bc.project.version.VersionService.VersionBuilderValidationResult). Since v6.4.UseVersionService.validateCreate(com.atlassian.jira.user.ApplicationUser, com.atlassian.jira.bc.project.version.VersionService.VersionBuilder)andVersionService.create(com.atlassian.jira.user.ApplicationUser, com.atlassian.jira.bc.project.version.VersionService.VersionBuilderValidationResult). Since v6.4UseVersionService.deleteVersionAndSwap(JiraServiceContext, DeleteVersionWithCustomFieldParameters)that supports swapping version in custom fields. Since v7.0.10since 7.0.10UseProjectRoleService.addActorsToProjectRole(java.util.Collection, com.atlassian.jira.security.roles.ProjectRole, com.atlassian.jira.project.Project, String, com.atlassian.jira.util.ErrorCollection)instead. Since v6.0.Will add project role actor associations for the given
actorsand checking thecurrentUserhas the correct permissions to perform the update operation. The passed inerrorCollectionwill contain any errors that are generated, such as permission violations.UseProjectRoleService.addActorsToProjectRole(java.util.Collection, com.atlassian.jira.security.roles.ProjectRole, com.atlassian.jira.project.Project, String, com.atlassian.jira.util.ErrorCollection)instead. Since v6.0.Will add default role actor associations based off the passed in
actorsand checking thecurrentUserhas the correct permissions to perform the update operation. The passed inerrorCollectionwill contain any errors that are generated, such as permission violations.UseProjectRoleService.createProjectRole(com.atlassian.jira.security.roles.ProjectRole, com.atlassian.jira.util.ErrorCollection)instead. Since v6.0.Will create the project role with the given
projectRole.getName(),projectRole.getDescription()and checking thecurrentUserhas the correct permissions to perform the create operation. The passed inerrorCollectionwill contain any errors that are generated, such as permission violations.UseProjectRoleService.deleteProjectRole(com.atlassian.jira.security.roles.ProjectRole, com.atlassian.jira.util.ErrorCollection)instead. Since v6.0.Will delete the given
projectRoleand checks thecurrentUserhas the correct permissions to perform the delete operation. This will also delete all ProjectRoleActor associations that it is the parent of. The passed inerrorCollectionwill contain any errors that are generated, such as permission violations.UseProjectRoleService.getAssociatedIssueSecuritySchemes(com.atlassian.jira.security.roles.ProjectRole, com.atlassian.jira.util.ErrorCollection)instead. Since v6.0.Will get all issue security scheme's that the specified projectRole is currently used in.
UseProjectRoleService.getAssociatedNotificationSchemes(com.atlassian.jira.security.roles.ProjectRole, com.atlassian.jira.util.ErrorCollection)instead. Since v6.0.Will get all notification scheme's that the specified projectRole is currently used in.
UseProjectRoleService.getAssociatedPermissionSchemes(com.atlassian.jira.security.roles.ProjectRole, com.atlassian.jira.util.ErrorCollection)instead. Since v6.0. Will get all permission scheme's that the specified projectRole is currently used in.UseProjectRoleService.getAssociatedWorkflows(com.atlassian.jira.security.roles.ProjectRole, com.atlassian.jira.util.ErrorCollection)instead. Since v6.0.Returns workflows and their actions that are associated with the given
ProjectRole. e.g. com.atlassian.jira.workflow.condition.InProjectRoleCondition workflow elements that block workflow transition unless the acting user is in the ProjectRole.UseProjectRoleService.getProjectRoleActors(com.atlassian.jira.security.roles.ProjectRole, com.atlassian.jira.project.Project, com.atlassian.jira.util.ErrorCollection)instead. Since v6.0.Will return a
DefaultRoleActorsfor the givenprojectRolechecking thecurrentUserhas the correct permissions to perform the get operation. The passed inerrorCollectionwill contain any errors that are generated, such as permission violations.UseProjectRoleService.getProjectIdsForUserInGroupsBecauseOfRole(java.util.List, com.atlassian.jira.security.roles.ProjectRole, String, String, com.atlassian.jira.util.ErrorCollection)instead. Since v6.0.Returns a Map of Lists. The key of the map is a Long, project id and the value of the map is a list of group names that the user is a member of for the project. This method is meant to provide an efficient means to discover which groups that are associated with a project role implicitly include the specified user in that project role. We allow you to specify a range of projectsToLimitBy so that you can perform only one query to find this information for many projects for a single projectRole.
UseProjectRoleService.getProjectRole(Long, com.atlassian.jira.util.ErrorCollection)instead. Since v6.0.Will return the project role with the given
id, and checking thecurrentUserhas the correct permissions to perform the operation. The passed inerrorCollectionwill contain any errors that are generated, such as permission violations.UseProjectRoleService.getProjectRoleActors(com.atlassian.jira.security.roles.ProjectRole, com.atlassian.jira.project.Project, com.atlassian.jira.util.ErrorCollection)instead. Since v6.0.Will return a {@link ProjectRoleActors) for the given <code>projectRole</code> and <code>project</code> checking the <code>currentUser</code> has the correct permissions to perform the get operation. The passed in <code>errorCollection</code> will contain any errors that are generated, such as permission violations.
UseProjectRoleService.getProjectRoleByName(String, com.atlassian.jira.util.ErrorCollection)instead. Since v6.0. Will return the project role with the givenname, and checking thecurrentUserhas the correct permissions to perform the operation. The passed inerrorCollectionwill contain any errors that are generated, such as permission violations.UseProjectRoleService.getProjectRoles(com.atlassian.jira.util.ErrorCollection)instead. Since v6.0.Get all the ProjectRoles available in JIRA. Currently this list is global.
UseProjectRoleService.getProjectsContainingRoleActorByNameAndType(String, String, com.atlassian.jira.util.ErrorCollection)instead. Since v6.0.Returns the
Project's which contain a role actor of the specified name and type within any role. This is a method that is provided so that you can efficiently tell which users or groups have been associated with any role within projects.Use#hasProjectRolePermission(com.atlassian.crowd.embedded.api.User, com.atlassian.jira.project.Project)instead. Since v6.0.Will have permission to modify roles if they are a JIRA admin or, if in enterprise, the user is a project administrator.
UseProjectRoleService.isProjectRoleNameUnique(String, com.atlassian.jira.util.ErrorCollection)instead. Since v6.0.Will tell you if a role name exists or not.
UseProjectRoleService.removeActorsFromProjectRole(java.util.Collection, com.atlassian.jira.security.roles.ProjectRole, com.atlassian.jira.project.Project, String, com.atlassian.jira.util.ErrorCollection)instead. Since v6.0.Will remove project role actor associations for the given
actorsand checking thecurrentUserhas the correct permissions to perform the update operation. The passed inerrorCollectionwill contain any errors that are generated, such as permission violations.UseProjectRoleService.removeAllRoleActorsByNameAndType(String, String, ErrorCollection)instead. Since v6.0.Will remove all role actors with the specified name and the specified type. This method should be used to clean up after the actual subject of the role actor has been deleted (ex. deleting a user from the system).
UseProjectRoleService.removeAllRoleActorsByNameAndType(String, String, com.atlassian.jira.util.ErrorCollection)(String, String)} instead. Since v6.0.Will remove all role actors with the specified name and the specified type. This method should be used to clean up after the actual subject of the role actor has been deleted (ex. deleting a user from the system).
UseProjectRoleService.removeAllRoleActorsByProject(com.atlassian.jira.project.Project, com.atlassian.jira.util.ErrorCollection)instead. Since v6.0. Will remove all role actors associated with the specified project. This method should be used to clean up just before the actual project has been deleted (ex. deleting a project from the system).UseProjectRoleService.removeDefaultActorsFromProjectRole(java.util.Collection, com.atlassian.jira.security.roles.ProjectRole, String, com.atlassian.jira.util.ErrorCollection)instead. Since v6.0.Will remove default actor associations based off the passed in
actors,projectRoleandactorTypeand checking thecurrentUserhas the correct permissions to perform the update operation. The passed inerrorCollectionwill contain any errors that are generated, such as permission violations.UseProjectRoleService.roleActorOfTypeExistsForProjects(java.util.List, com.atlassian.jira.security.roles.ProjectRole, String, String, com.atlassian.jira.util.ErrorCollection)instead. Since v6.0.Returns a list of projectId's for which the role actor of the specified type exists in the project for the provided projectRole. This is a method that is meant to efficiently allow discovery of whether a UserRoleActor exists in a project role for a subset of projects.
UseProjectRoleService.setActorsForProjectRole(java.util.Map, com.atlassian.jira.security.roles.ProjectRole, com.atlassian.jira.project.Project, com.atlassian.jira.util.ErrorCollection)instead. Since v6.0.Will set the project role actor associations for the given
newRoleActorsand checking thecurrentUserhas the correct permissions to perform the update operation. The passed inerrorCollectionwill contain any errors that are generated, such as permission violations.UseProjectRoleService.updateProjectRole(com.atlassian.jira.security.roles.ProjectRole, com.atlassian.jira.util.ErrorCollection)instead. Since v6.0. Will updateprojectRole, checking thecurrentUserhas the correct permissions to perform the update operation. The passed inerrorCollectionwill contain any errors that are generated, such as permission violations.UseProjectRoleService.removeAllRoleActorsByNameAndType(String, String)instead. Since v6.0.Will validate removing all role actors with the specified name and the specified type. This method should be used before clean up after the actual subject of the role actor has been deleted (ex. deleting a user from the system). Validation error wil be reported when name does not exists, type does not exists or user performing validation does not have administrative rights
since 8.20. Using postProcessingFilter parameter may cause performance issues. Especially when the predicate matches fraction of users smaller than limit set by limitResults/maxResults.since 8.20. UseUserSearchParams.Builder.limitResults(int)instead to avoid returning excessive number of users.since 8.20. Using postProcessingFilter field may cause performance issues.UseUserService.createUser(CreateUserValidationResult)instead. Since v7.0.UseUserService.createUser(CreateUserValidationResult)instead. Since v7.0.Since v7.0.UseUserService.createUser(CreateUserValidationResult)instead. Since v7.0.UseUserService.removeUser(ApplicationUser, DeleteUserValidationResult)instead. Since v6.0.UseUserService.UpdateUserValidationResult.getApplicationUser()instead. Since v6.0.com.atlassian.jira.bc.user.UserService.validateAddUserToApplication(ApplicationUser, ApplicationKey) UseUserService.validateAddUserToApplication(ApplicationUser, ApplicationUser, ApplicationKey)instead. Since v7.0UseUserService.validateCreateUser(CreateUserRequest)instead. Since v7.0.UseUserService.validateCreateUser(CreateUserRequest)instead. Since v7.0.UseUserService.validateCreateUser(CreateUserRequest)instead. Since v7.0.UseUserService.validateCreateUser(CreateUserRequest)instead. Since v7.0.UseUserService.validateCreateUser(CreateUserRequest)instead. Since v7.0.Depreciated as of 7.3. Method was used to check if transition can be added to a status (status had to have at least one outgoing transition). After fixing https://jira.atlassian.com/browse/JRA-19091 this is no longer needed.UseSubTaskBeanImpl.addSubTask(Long, com.atlassian.jira.issue.Issue, com.atlassian.jira.issue.Issue)instead. Since v5.0.you should useChart.getBase64Image()JRA-21854 images should be rendered using data uri. Please useChartHelper.generateInline(int, int)Use #getImageMapHtmluse inline chartssince 9.14 would always return true.UseComponentAccessor.getOSGiComponentInstanceOfType(Class)every time it is needed, instead. In the rare instances where this has unacceptable performance consequences, consider using aServiceTrackeror other similar enhanced access methods available through OSGi and through the plugin system in general. Since v7.0.0.Deprecated since v7.0. You just shouldn't have GVs any moreUseConstantsManager.getStatus(java.lang.String)instead. Deprecated since v7.0UseConstantsManager.insertIssueType(String, Long, String, String, Long)instead. Since v6.3.Since 7.0. Do not use this method!!! UseIssueTypeManager.removeIssueType(String, String).com.atlassian.jira.config.feature.BootstrapDarkFeatureManager.isFeatureEnabledForCurrentUser(String) - since 7.6 all flags are created as off by default- since 7.6 all flags are created as off by default, if you want your flag to be switched on use onByDefaultSince 7.0 UseIssueConstantFactory.createIssueType(IssueTypeDTO)Since 7.0 UseIssueConstantFactory.createPriority(PriorityDTO)Since 7.0 UseIssueConstantFactory.createResolution(ResolutionDTO)Since 7.0 UseIssueConstantFactory.createStatus(StatusDTO)UseIssueTypeManager.createIssueType(String, String, Long)instead. Since v6.3.UseIssueTypeManager.updateIssueType(com.atlassian.jira.issue.issuetype.IssueType, String, String, Long)instead. Since v6.3.since v7.6. Use priority schemesPrioritySchemeManager.getDefaultOption(IssueContext)since v7.6. Use priority schemesPrioritySchemeManager.setDefaultOption(FieldConfig, String)since 8.15. UseUiSettingsStateManager.getStateHash().in Jira 6.0 -- the common header is always enabled.Since v7.0since 8.15. UseUiSettingsStateManager.invalidateStateHash().UseSubTaskManager.getParentIssueId(Issue)instead. Since v6.4.UseSubTaskManager.getSubTaskIssueType(String)instead. Since v5.0.UseDatabaseAccessor.runInManagedTransaction(Function)instead, so that you get a managed, nestable transaction. Since v7.5.0.since 8.3, to be removed in 9.0In 6.2.3 as this method does not properly throw events. UseJsonEntityPropertyManager.put(com.atlassian.jira.user.ApplicationUser, String, Long, String, String, BiFunction, boolean)instead.Since v5.0usecom.atlassian.jira.event.issue.IssueEventManager#dispatchEvent(Long, com.atlassian.jira.issue.Issue, com.atlassian.crowd.embedded.api.User, boolean)instead.Since v5.0Since v5.0Since v5.0Since v5.0Since v5.0Since v5.0com.atlassian.jira.event.issue.IssueEventDispatcher.dispatchEvent(Long, Issue, Map, ApplicationUser) Since v5.0usecom.atlassian.jira.event.issue.IssueEventManager#dispatchEvent(Long, com.atlassian.jira.issue.Issue, java.util.Map, com.atlassian.crowd.embedded.api.User, boolean)instead.Please callIssueEventListener.workflowEvent(IssueEvent)Please callIssueEventListener.workflowEvent(IssueEvent)Please callIssueEventListener.workflowEvent(IssueEvent)Please callIssueEventListener.workflowEvent(IssueEvent)Please callIssueEventListener.workflowEvent(IssueEvent)Please callIssueEventListener.workflowEvent(IssueEvent)Please callIssueEventListener.workflowEvent(IssueEvent)Please callIssueEventListener.workflowEvent(IssueEvent)Please callIssueEventListener.workflowEvent(IssueEvent)Please callIssueEventListener.workflowEvent(IssueEvent)Please callIssueEventListener.workflowEvent(IssueEvent)Please callIssueEventListener.workflowEvent(IssueEvent)Please callIssueEventListener.workflowEvent(IssueEvent)since v6.4.10, please useIssueEventManager.dispatchEvent(IssueEventBundle).since v6.4.10, please useIssueEventManager.dispatchEvent(IssueEventBundle).since v6.4.10, please useIssueEventManager.dispatchEvent(IssueEventBundle).since v6.4.10, please useIssueEventManager.dispatchEvent(IssueEventBundle).since v6.4.10, please useIssueEventManager.dispatchEvent(IssueEventBundle).since v6.4.10, please useIssueEventManager.dispatchEvent(IssueEventBundle).since v6.4.10, please useIssueEventManager.dispatchEvent(IssueEventBundle).since v6.4.10, please useIssueEventManager.dispatchEvent(IssueEventBundle).since v6.4.10, please useIssueEventManager.dispatchEvent(IssueEventBundle).since v6.4.10, please useIssueEventManager.dispatchEvent(IssueEventBundle).since v6.4.10, please useIssueEventManager.dispatchEvent(IssueEventBundle).since v6.4.10, please useIssueEventManager.dispatchEvent(IssueEventBundle).since v6.4.10, please useIssueEventManager.dispatchEvent(IssueEventBundle).since v6.4.10, please useIssueEventManager.dispatchEvent(IssueEventBundle).since v6.4.10, please useIssueEventManager.dispatchEvent(IssueEventBundle).Always returns `true`. The event is emitted only if the value changes.Logic to create events was moved toUserEventFactory. For dispatching messages, prefer usingEventPublisherdirectly.Logic to create events was moved toUserEventFactory. For dispatching messages, prefer usingEventPublisherdirectly.since 4.2. This method is not future-proof; as fields get added to configurations, the 'id' sequence might change for the field you intended to use. UseFieldConfigurations.FieldConfiguration.hideFields(String)instead.since 4.2. This method is not future-proof; as fields get added to configurations, the 'id' sequence might change for the field you intended to use. UseFieldConfigurations.FieldConfiguration.showFields(String)instead.Now the edit button always takes you to the workflow designer. UseViewWorkflows.edit(String)insteaduseSubtasks.enable()instead.UseAdministration.addGlobalPermission(com.atlassian.jira.permission.GlobalPermissionKey, String)instead. Since v6.2.5.UseAdministration.removeGlobalPermission(com.atlassian.jira.permission.GlobalPermissionKey, String)instead. Since v6.2.5.since 7.0.1. useAdministration#restoreNotSetupInstance(License)insteadall 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()since 7.0.1, use restoreNotSetupInstanceuseBackdoor.restoreBlankInstance(License)instead, since 7.0.1useBackdoor.restoreDataFromResource(String)insteaduseBackdoor.restoreInstance(String, License)instead, since 8.15.0useBackdoor.restoreInstance(String, License)instead, since 8.15.0works the same asIssueNavigatorNavigationImpl.gotoNavigator().JRADEV-14514 - The issues column has been removed from the filter listJRADEV-14514 - The issues column has been removed from the filter list, so this always returns0L, now.JRADEV-14514 - The issues column has been removed from the filter listremove it as part of DBR-107UseAbstractIssue.getParentObject()instead.UseAttachment.getAuthorObject()instead. Since v6.0.since v6.0. To be removed in Jira 10.UseTemporaryWebAttachmentManager.convertTemporaryAttachments(com.atlassian.jira.user.ApplicationUser, com.atlassian.jira.issue.Issue, java.util.List<java.lang.String>)instead. Since v6.4. To be removed in Jira 10.UseChangeHistory.getAuthorKey()instead. Since v6.0.UseChangeHistory.getAuthorObject()instead. Since v6.0.Returns the author of this Change
UseChangeHistory.getAuthorDisplayName()instead. Since v5.0.UseChangeHistory.getAuthorObject()instead. Since v5.0.UseChangeHistoryGroup.getUserKey()instead (for clarity). Since v6.0.UseComment.getAuthorKey()orComment.getAuthorApplicationUser()instead. Since v6.0.UseComment.getAuthorKey()orComment.getAuthorApplicationUser()instead. Since v6.0.UseComment.getAuthorApplicationUser()instead. Since v6.0.UseComment.getUpdateAuthorApplicationUser()instead. Since v6.0.UseComment.getUpdateAuthorApplicationUser()instead. Since v6.0.Get the user that performed the update
UseCommentManager.create(Issue issue, ApplicationUser author, String body, boolean dispatchEvent)instead. Since 6.0.UseMutableComment.setAuthor(com.atlassian.jira.user.ApplicationUser)instead. Since v6.0.UseMutableComment.setUpdateAuthor(com.atlassian.jira.user.ApplicationUser)instead. Since v6.0.UseRecentCommentManager.getRecentComments(com.atlassian.jira.issue.search.SearchRequest, com.atlassian.jira.user.ApplicationUser)instead. Since v6.0.Return an iterator over all the comments from any issues in the search request that the user can see
Please useIssueContext.getIssueType(). Deprecated since v7.0UseGroupConverter.getGroup(String)instead. Since v5.0.UseUserConverter.getHttpParameterValue(ApplicationUser)orUserConverter.getDbString(ApplicationUser)instead. Since v6.0.UseUserConverter.getUserFromDbString(String)instead. Since v6.0.UseUserConverter.getUserFromDbString(String)instead. Since v6.0.UseUserConverter.getUser(String)instead. Since v5.0.UseCustomFieldUtils.buildJiraIssueContexts(boolean, Long[], com.atlassian.jira.project.ProjectManager)instead. Since v6.4.As of 9.17.0, useMultipleCustomFieldType.getOptions(FieldConfig)instead.UseOption.getChildOptions()instead. Since v9.17since 8.13 useCustomFieldValuePersister.getValues(Set)insteadUse #getSearchRequestAppender().appendInclusiveSingleValueClause()Use #getSearchRequestAppender().appendInclusiveSingleValueClause()Use #getSearchRequestAppender().appendInclusiveSingleValueClause()since 7.0, useDocumentIssueImpl.getComponents()insteadsince v8.15 use theFieldConfig.getConfigurableField().Since v7.0UseFieldConfigSchemeManager.getRelevantConfigScheme(Project, ConfigurableField)instead. Since v6.3.7.Use ofGenericValueis discouraged. Deprecated since: v4.0. UseIssueTypeSchemeManager.getConfigScheme(Project)instead.UseIssueTypeSchemeManager.getDefaultIssueType(Project)instead. Since v5.2.Use ofGenericValueis discouraged. Deprecated since: 3.9. UseIssueTypeSchemeManager.getIssueTypesForProject(Project)instead.since 8.12 useFieldConfigSchemePersister.filterRelevantFields(IssueContext, Set)insteadAs of 7.2, please useCustomField.getAssociatedIssueTypes()UseField.getName(),CustomField.getDescription(), etc. Since v3.0.As of 9.17.0, please useCustomField.getOptions(JiraContextNode)insteadAs of 9.17.0, please useCustomField.getOptions(FieldConfig)insteadUseCustomFieldManager.removeCustomField(CustomField)instead. Since v7.0.UseFieldManager.isExistingCustomField(java.lang.String)orFieldManager.isCustomFieldId(java.lang.String)instead. Since v6.5.Current implementation of this method is not very good performance wise. UseColumnLayout.getColumnLayoutItems()instead. Since 6.3.3UseFieldLayout.getVisibleLayoutItems(com.atlassian.jira.project.Project, java.util.List)instead. Since v6.2.UseFieldLayoutManager.addSchemeAssociation(com.atlassian.jira.project.Project, Long)instead. Since v5.2.UseFieldLayoutManager.getFieldLayout(com.atlassian.jira.issue.Issue)instead. Since v5.0.UseFieldLayoutManager.getProjectsUsing(FieldConfigurationScheme)instead. Since v6.4.UseFieldLayoutManager.getProjectsUsing(FieldLayoutScheme)instead. Since v6.4.UseFieldLayoutManager.getProjectsUsing(FieldLayout)instead. Since v6.4.UseFieldLayoutManager.removeSchemeAssociation(com.atlassian.jira.project.Project, Long)instead. Since v5.2.UseFieldLayoutScheme.getProjectsUsing()instead. Since v6.4.UseDefaultUserBeanFactory.createBean(com.atlassian.jira.user.ApplicationUser, com.atlassian.jira.user.ApplicationUser)orDefaultUserBeanFactory.createBean(com.atlassian.jira.user.ApplicationUser, com.atlassian.jira.user.ApplicationUser, JiraBaseUrls, com.atlassian.jira.util.EmailFormatter, com.atlassian.jira.timezone.TimeZoneManager)UseDefaultUserBeanFactory.createBean(com.atlassian.jira.user.ApplicationUser, com.atlassian.jira.user.ApplicationUser)orDefaultUserBeanFactory.createBean(com.atlassian.jira.user.ApplicationUser, com.atlassian.jira.user.ApplicationUser, JiraBaseUrls, com.atlassian.jira.util.EmailFormatter, com.atlassian.jira.timezone.TimeZoneManager)UseDefaultUserBeanFactory.createBean(com.atlassian.jira.user.ApplicationUser, com.atlassian.jira.user.ApplicationUser)orDefaultUserBeanFactory.createBean(com.atlassian.jira.user.ApplicationUser, com.atlassian.jira.user.ApplicationUser, JiraBaseUrls, com.atlassian.jira.util.EmailFormatter, com.atlassian.jira.timezone.TimeZoneManager)UseDefaultUserBeanFactory.createBeanCollection(java.util.Collection, com.atlassian.jira.user.ApplicationUser)orDefaultUserBeanFactory.createBeanCollection(java.util.Collection, com.atlassian.jira.user.ApplicationUser, JiraBaseUrls, com.atlassian.jira.util.EmailFormatter, com.atlassian.jira.timezone.TimeZoneManager)UseDefaultUserBeanFactory.createBeanCollection(java.util.Collection, com.atlassian.jira.user.ApplicationUser)orDefaultUserBeanFactory.createBeanCollection(java.util.Collection, com.atlassian.jira.user.ApplicationUser, JiraBaseUrls, com.atlassian.jira.util.EmailFormatter, com.atlassian.jira.timezone.TimeZoneManager)UseDefaultUserBeanFactory.createBeanCollection(java.util.Collection, com.atlassian.jira.user.ApplicationUser)orDefaultUserBeanFactory.createBeanCollection(java.util.Collection, com.atlassian.jira.user.ApplicationUser, JiraBaseUrls, com.atlassian.jira.util.EmailFormatter, com.atlassian.jira.timezone.TimeZoneManager)UseDefaultUserBeanFactory.createBeanCollection(java.util.Collection, com.atlassian.jira.user.ApplicationUser)orDefaultUserBeanFactory.createBeanCollection(java.util.Collection, com.atlassian.jira.user.ApplicationUser, JiraBaseUrls, com.atlassian.jira.util.EmailFormatter, com.atlassian.jira.timezone.TimeZoneManager)UseDefaultUserBeanFactory.createBeanCollection(java.util.Collection, com.atlassian.jira.user.ApplicationUser)orDefaultUserBeanFactory.createBeanCollection(java.util.Collection, com.atlassian.jira.user.ApplicationUser, JiraBaseUrls, com.atlassian.jira.util.EmailFormatter, com.atlassian.jira.timezone.TimeZoneManager)UseDefaultUserBeanFactory.createBeanCollection(java.util.Collection, com.atlassian.jira.user.ApplicationUser)orDefaultUserBeanFactory.createBeanCollection(java.util.Collection, com.atlassian.jira.user.ApplicationUser, JiraBaseUrls, com.atlassian.jira.util.EmailFormatter, com.atlassian.jira.timezone.TimeZoneManager)UseFieldScreenRendererFactory.getFieldScreenRenderer(com.atlassian.jira.issue.Issue, com.atlassian.jira.issue.operation.IssueOperation)instead. Use FieldPredicates.isCustomField() in the version that takes a predicate if you only want custom fields. Since v6.2.UseIssueTypeScreenSchemeManager.associateWithDefaultScheme(com.atlassian.jira.project.Project)instead. Since v6.4.UseIssueTypeScreenSchemeManager.getIssueTypeScreenScheme(com.atlassian.jira.project.Project)instead. Since v6.4.since 8.10 useFieldIndexer.addIndex(Document, Issue, CustomFieldPrefetchedData)insteadsince 8.12.1 useFieldIndexerWithStats.resetStats()since 8.12.1 useFieldIndexerWithStats.getStatsAndResetSnapshot()since 8.12.1 useFieldIndexerWithStats.getStats()since 8.10 implementAbstractCustomFieldIndexer.addDocumentFieldsNotSearchable(Document, Issue, CustomFieldPrefetchedData)insteadsince 8.10 implementAbstractCustomFieldIndexer.addDocumentFieldsSearchable(Document, Issue, CustomFieldPrefetchedData)insteadsince 8.12.1 useIndexingStatsEventPublisher.publishSlowIndexersStats(Iterable)Since Jira 9.0 issue version is requiredSince v5.0 useIssueIndexingService.deIndex(Issue)instead. Since v7.0 useIssueIndexingService.deIndex(Issue)instead.Call this asIssueIndexingService.reIndex(Issue)instead. Since v7.0.Since v6.4, useIssueIndexManager.reIndex(Issue, IssueIndexingParams). Since v7.0, useIssueIndexingService.reIndex(Issue, IssueIndexingParams).Call this asIssueIndexingService.reIndex(Issue, IssueIndexingParams)instead. Since v7.0.Since v5.0. UseIssueIndexManager.reIndex(Issue)instead. Since v7.0, useIssueIndexingService.reIndex(Issue)instead.Call this asIssueIndexingService.reIndexAll()instead. Since v7.0.Call this asIssueIndexingService.reIndexAll(Context, boolean, boolean)instead. Since v7.0.since v6.4 useIssueIndexManager.reIndexAll(Context, boolean, IssueIndexingParams, boolean)instead. Since v7.0 useIssueIndexingService.reIndexAll(Context, boolean, IssueIndexingParams, boolean)instead.Call this asIssueIndexingService.reIndexAll(Context, boolean, IssueIndexingParams, boolean)instead. Since v7.0.Call this asIssueIndexingService.reIndexComments(Collection)instead. Since v7.0.Call this asIssueIndexingService.reIndexComments(Collection, Context)instead. Since v7.0.Call this asIssueIndexingService.reIndexComments(Collection, Context, boolean)instead. Since v7.0.Call this asIssueIndexingService.reIndexIssueObjects(Collection)instead. Since v7.0.Call this asIssueIndexingService.reIndexIssueObjects(Collection, IssueIndexingParams)instead. Since v7.0.Call this asIssueIndexingService.reIndexIssueObjects(Collection, IssueIndexingParams, boolean)instead. Since v7.0.Call this asIssueIndexingService.reIndexIssues(IssuesIterable, Context)instead. Since v7.0.Call this asIssueIndexingService.reIndexIssues(IssuesIterable, Context, IssueIndexingParams)instead. Since v7.0.Since v5.0, useIssueIndexManager.reIndexIssueObjects(Collection)instead. Since v7.0, useIssueIndexingService.reIndexIssueObjects(Collection)instead.Call this asIssueIndexingService.reIndexWorklogs(Collection)instead. Since v7.0.Call this asIssueIndexingService.reIndexWorklogs(Collection, Context)instead. Since v7.0.Call this asIssueIndexingService.reIndexWorklogs(Collection, Context, boolean)instead. Since v7.0.useThreadLocalSearcherCache.stopAndCloseSearcherContext(); should only be used in JIRA core internally;UseIssue.getComponents(). Since v7.0Use the Data object getters instead. Since v5.0.Please useIssue.getIssueType(). Deprecated since v7.0UseIssue.getParentObject()instead.UseIssue.getPriority()instead. Since v7.0please use getProjectObject (this still implicitly relies on the GV), but it is a start!UseIssue.getResolution()instead. Since v7.0UseIssue.getSecurityLevelId()instead. Since v5.2.since 7.0. UseIssue.getStatus()instead.You should construct this yourself if at all possible, or useIssueFactory.getIssue(org.ofbiz.core.entity.GenericValue)instead.UseIssueImpl.getParentObject()instead.Use#createIssueObject(User, Issue)instead. Since v5.0Use#createIssueObject(User, java.util.Map)instead. Since v5.0.UseIssueManager.createIssueObject(String, Map)instead since v5.0.Use#deleteIssue(com.atlassian.crowd.embedded.api.User, Issue, com.atlassian.jira.event.type.EventDispatchOption, boolean)instead. Since v5.0.UseIssueManager.deleteIssueNoEvent(com.atlassian.jira.issue.Issue)instead. Since v5.0.UseIssueManager.getIssueObject(Long)instead.UseIssueManager.getIssueObject(String)instead.UseIssueManager.getIssueObjectByWorkflow(Long)instead. Since v5.0UseVersionManager.getIssueIdsWithAffectsVersion(com.atlassian.jira.project.version.Version),VersionManager.getIssueIdsWithFixVersion(com.atlassian.jira.project.version.Version), orProjectComponentManager.getIssueIdsWithComponent(com.atlassian.jira.bc.project.component.ProjectComponent)instead. Since v6.1.UseIssueManager.getIssueObjects(java.util.Collection)instead. Since v5.0UseVersionManager.getIssueIdsWithAffectsVersion(com.atlassian.jira.project.version.Version),VersionManager.getIssueIdsWithFixVersion(com.atlassian.jira.project.version.Version), orProjectComponentManager.getIssueIdsWithComponent(com.atlassian.jira.bc.project.component.ProjectComponent)instead. Since v6.1.only used in test cases, should use a search provider instead.UseIssueManager.getWatchersFor(Issue)instead. Since v6.0.Since 7.1 beucase it generate old fashioned URLs. UseLabelUtil.getLabelSearchPath(ApplicationUser, Long, String)instead.Since 7.1 beucase it generate old fashioned URLs. UseLabelUtil.getLabelSearchPath(ApplicationUser, String)instead.Since 7.1 beucase it generate old fashioned URLs. UseLabelUtil.getLabelSearchPathForProject(ApplicationUser, Long, Long, String)instead.Since 7.1 beucase it generate old fashioned URLs. UseLabelUtil.getLabelSearchPathForProject(ApplicationUser, Long, String)instead.No replacement needed; just stop calling it. Since v7.0.Use#removeIssueLinks(com.atlassian.jira.issue.Issue, com.atlassian.crowd.embedded.api.User)instead. Since v5.0.No longer relevant because of introduction of Remote Issue Links. Since v5.0.UseMutableIssue.setProjectObject(com.atlassian.jira.project.Project)andMutableIssue.setNumber(Long)to change issue. Since v6.1UseMutableIssue.setProjectObject(com.atlassian.jira.project.Project)instead. Since v5.0.UseMutableIssue.setSecurityLevelId(Long)instead. Since v5.0.Use the Object's Service or Manager to save values. Since v5.0. DO NOT USE THIS as it overwrites all the fields of the issue which can result in difficult to reproduce bugs Prefer to use QueryDslAccessor to change only needed fieldsThere are countless simpler and faster ways to get anI18nHelperand ask it to translate something for you. AskingIssueOperationsto do it does not make any sense. Since v6.3.As of JIRA 6.0, issue pager is no longer generated on the server side. This method will do nothing.Not used for resolutions. Since v5.0.UsePermissionsFilterGenerator.getQuery(ApplicationUser, Collection)instead, since 7.10Since 6.3.4. TheSearchContextparameter is no longer needed. UseNavigatorStructureChecker.checkSearchRequest(com.atlassian.query.Query)UseSearchRequest.setOwner(com.atlassian.jira.user.ApplicationUser)instead. Since v6.0. Set the owner of the SearchRequest.Since 6.3.3, useSearchRequestFactory.createFromQuery(SearchRequest, ApplicationUser, com.atlassian.query.Query)instead.UseSearchRequestManager.visitAll(Visitor)instead. Since v5.2.UseSearchRequestManager.getSearchRequestOwner(Long id)instead. Since v6.0.Return the owner of the passed SearchRequest. This is mainly used for permission checks.
UseIssueSecurityLevelManager.getAllIssueSecurityLevels()instead. Since v5.0.UseIssueSecurityLevelManager.getAllSecurityLevelsForUser(ApplicationUser)instead. Since v5.0.UseIssueSecurityLevelManager.getSecurityLevel(long)instead. Since v5.0.UseIssueSecurityLevelManager.getSecurityLevel(long)instead. Since v5.0.UseIssueSecurityLevelManager.getDefaultSecurityLevel(com.atlassian.jira.project.Project)instead. Since v5.0.UseIssueSecurityLevelManager.getIssueSecurityLevels(long)instead. Since v5.0.UseIssueSecurityLevelManager.getIssueSecurityLevelsByName(String)instead. Since v5.0.UseIssueSecurityLevelManager.getSecurityLevelsForUserByName(ApplicationUser, String)instead. Since v5.0.UseIssueSecurityLevelManager.getSecurityLevel(long)!= null instead. Since v5.0.UseIssueSecuritySchemeManager.getPermissionsBySecurityLevel(Long)instead. Since v5.2.com.atlassian.jira.issue.security.IssueSecuritySchemeManager.getEntities(GenericValue, Long, String) Not used - presumably this was invented in SchemeManager for Permission Schemes.Never worked for String anyway. Since v6.4.com.atlassian.jira.issue.security.IssueSecuritySchemeManager.getEntities(GenericValue, String, Long) Not used - presumably this was invented in SchemeManager for Permission Schemes.UseIssueSecuritySchemeManager.getPermissionsBySecurityLevel(Long)instead. Since v5.2.UseIssueSecuritySchemeManager.getIssueSecurityLevelScheme(Long)instead. Since v5.2.Use #getSearchRequestAppender().appendInclusiveSingleValueClause()Use #getSearchRequestAppender().appendInclusiveSingleValueClause()Use #getSearchRequestAppender().appendInclusiveSingleValueClause()com.atlassian.jira.issue.statistics.LabelsStatisticsMapper.getSearchUrlSuffix(Object, SearchRequest) Use #getSearchRequestAppender().appendInclusiveSingleValueClause()Use #getSearchRequestAppender().appendInclusiveSingleValueClause()Use #getSearchRequestAppender().appendInclusiveSingleValueClause()Use #getSearchRequestAppender().appendInclusiveSingleValueClause()UseStatus.getStatusCategory()instead. Since v6.1.UseStatus.getStatusCategory()instead. Since v6.1.use @{#next()}UseIssueVoterAccessor.getVoterUserkeys(com.atlassian.jira.issue.Issue)instead. Since v6.0.UseVoteManager.addVote(com.atlassian.jira.user.ApplicationUser, com.atlassian.jira.issue.Issue)instead. Since v6.0.UseVoteManager.getVotersFor(com.atlassian.jira.issue.Issue, java.util.Locale)instead. Since v6.0.UseVoteManager.getVoterUserkeys(com.atlassian.jira.issue.Issue)instead. Since v6.0.UseVoteManager.getVoterUsernames(com.atlassian.jira.issue.Issue)instead. Since v6.0.UseVoteManager.hasVoted(com.atlassian.jira.user.ApplicationUser, com.atlassian.jira.issue.Issue)instead. Since v6.0.UseVoteManager.removeVote(com.atlassian.jira.user.ApplicationUser, com.atlassian.jira.issue.Issue)instead. Since v6.0.UseIssueWatcherAccessor.getWatcherKeys(com.atlassian.jira.issue.Issue)instead. Since v6.0.UseWorklog.getAuthorKey()instead. Since v6.0.UseApplicationUser.getDisplayName()ofWorklog.getAuthorObject()instead. Since v6.0.UseWorklog.getAuthorKey()instead. Since v6.0.UseApplicationUser.getDisplayName()ofWorklog.getUpdateAuthorObject()instead. Since v6.0.use #mockExpectedRedirect(String)UseQueryCreationContext.getUser()instead. Since v5.0.since 6.1 useQueryCreationContext.getApplicationUser()insteadUseDefaultLicenseDetails.getMaintenanceExpiry()insteaduseLicenseCountService.flushBillableUsersCache(). Since v7.0. Eventually we want to remove this method in favour of the one with a more descriptive name.since 7.0.0 No replacement, generate your own messagesince 7.0.0 No replacement, generate your own messagesince 5.0 No replacement, generate your own messagesince 7.0.0 No replacement, generate your own messageUseLicenseDetails.getPurchaseDate(DateTimeFormatter)instead. Since v7.1not for external usage, subject to removingnot for external usage, subject to removingAs of Jira 10.2 this signature is deprecated due to theme supports introduced. UseUploadService.uploadLogo(ImageDescriptor, LookAndFeelBean, boolean)instead, as it additionally defines for what theme logo is uploaded.UseMailServerManager.isDefaultSMTPMailServerDefined()instead. Since 5.0just use Joiner.on(",").join(addresses)useMailingListCompiler.prepareEmail(Set, String, String, Long, String, Map, MailThreader)and add emails to desired queue by yourselfPlease useTemplateUser.getEmailAddress(). Since v4.3please useTemplateUser.getDisplayName(). Since v4.3useMailAttachmentsManager.processImages(String)instead. Will be removed in Jira 9.0 because name of this method no longer relevant. Removing this method will affect mail templatesUseMockIssue.getComponents(). Since v7.0UseMockFeatureManager.disableFeature(Feature)insteadUseMockFeatureManager.enableFeature(CoreFeatures)insteadUseMockFeatureManager.enableFeature(Feature)insteadUseNotificationRecipient.getUser()instead. Since v6.0.Not used - presumably this was invented in SchemeManager for Permission Schemes.Never worked for Strings. Since v6.4.Not used - presumably this was invented in SchemeManager for Permission Schemes.since 9.15 inject and use OfBizConnectionFactory instead.Use the Data object getters instead. Since v5.0.Use the Data object getters instead. Since v5.0.Use the Data object getters instead. Since v5.0.Use the Data object getters instead. Since v5.0.Use the Object's Service or Manager to save values. Since v5.0.useSingleSelect.allSuggestions()as this method is prone to return wrong results due to race conditions. UsingSingleSelect.getSuggestionsTimed()will enforce clients to execute timed assertions and improve reliability of the testsuseEditIssueDialog.setDueDate(String)and take care of formatting yourself.Datedoesn't understand timezones, which is essential for converting to a day/month/year format.Using this method will open you up to flaky tests when the test runner and JIRA instances are on different computers with different timezone settings.
this functionality no longer existthis functionality no longer existthis feature no longer existsuseEditScreenTab.getFieldNames()This method used to be prone to return wrong results due to race conditions. It was adjusted to fallback toEditScreenTab.getFieldNames()at .now() moment. UsingEditScreenTab.getFieldNames()} directly will enforce clients to execute timed assertions and improve reliability of the tests.there is no such functionality in addsubtask type dialogthere is no such functionality in addsubtask type dialogthere is no such functionality in addsubtask type dialogNot available in UI anymore, does not filter by username only, internally callsUserBrowserPage.filterByEmail(java.lang.String)Not available in UI anymore, does not filter by username only, internally callsUserBrowserPage.filterByUserSearch(java.lang.String)since v7.2 There is no longer a change project type action in the view projects. You can do this by going to the edit project page. Or clicking edit for this project on the view projects page.since v7.2 There is no longer a change project type action in the view projects.useEditPermissionsSinglePage.GrantPermissionsDialoginsteadsince 6.4. UseMailSetupPage.submitWithoutBinding()instead as you cannot be sure if you'll end up on JIRA's dashboard or an Onboarding flow after setup finishes.since 6.4. UseMailSetupPage.submitDisabledEmailWithoutBinding()instead as you cannot be sure if you'll end up on JIRA's dashboard or an Onboarding flow after setup finishes.- UseViewIssuePage.getAssigneeTimed()with a Poller and Matcher for more reliabilityas no more information is stored in the header. UseProjectConfigPageTab.getProjectSettingsHeader()if you want to get the new header. Otherwise, if you want project information such as the key, use the backdoor for the project.USE permissions will be changing significantly in JIRA 7.0 . If you are using this method, then you will need to watch out for announcements in 7.0 Developer upgrade guide. Since v6.2.5UsePermissionContext.getProjectObject()instead. Since v5.0.UsePermissionContext.hasIssuePermissions()instead. Since v5.0.com.atlassian.jira.permission.PermissionContextFactory.getPermissionContext(OperationContext, Issue) UsePermissionContextFactory.getPermissionContext(Issue, ActionDescriptor)instead. Since v5.0.UsePermissionContextFactory.getPermissionContext(Issue)orPermissionContextFactory.getPermissionContext(Project)instead. Since v5.0.Please use i18nBean.getText() instead. Since 5.0getTotalEntryCountinstead. Since v6.4.CompareAttachmentArchive.getTotalEntryCount()with size ofAttachmentArchive.getEntries()instead. Since v6.4.Abbreviate the path (name) in views. It is view-specific operation. Since v6.4.since 8.10 useCustomFieldTypeModuleDescriptors.getUnorderedCustomFieldTypes()and sort only when neededThis method should not be used by new code, and will be removed when plugins is upgraded.Should be removed in next breaking API release (Jira 9.0) when all plugins should switch toPluginTransactionEndEventor toLifecycleAware.onStart()whereonStart()would be triggered byPluginTransactionEndEvent.UseUserFormatManager.formatUserkey(String, String, String)orUserFormatManager.formatUsername(String, String, String)instead. Since v6.0.UseUserFormats.formatter(String)instead. Since v6.0.UseJiraHelper.getProject(). Since v6.5You should generally never need to use this API, instead you should rely on the page builder service delivering data to the client side and exposing it via theWRM.data.claimJavaScript API.UseWebResourceDataProviderinstead. Since v6.4.UsePortalPage.Builder.owner(com.atlassian.jira.user.ApplicationUser)instead. Since v6.0.since v7.1, kept to avoid breaking binary compatibility, also defined inSharedEntityAccessor.search(com.atlassian.jira.sharing.search.SharedEntitySearchParameters, com.atlassian.jira.user.ApplicationUser, int, int)UseBrowseContext.getIssueSearchPath()instead.only use this if you need to utilize an older API methodUseProject.getProjectLead(), which returns application users, instead. Since v6.0.UseProjectManager.getDefaultAssignee(Project, java.util.Collection)which allows for multiple components. Since v4.4.since v7.1.1. UseProjectManager.removeProjectIssues(Project, Context)All projects created via a template will be redirected to the Browse Project page. This value will be ignored.All projects created via a template will be redirected to the Browse Project page. This value will be ignored.useUpdateProjectParameters.leadUserKeyandUpdateProjectParameters.getLeadUserKey()insteaduseUpdateProjectParameters.leadUserKeyandUpdateProjectParameters.getLeadUserKey()insteadsince version 6.0Please useVersion.getProject(). Since v7.0Since JIRA version 7.0.1, this is deprecated on favour ofVersionManager.createVersion(String, java.util.Date, java.util.Date, String, Long, Long, boolean)which lets you specify thestartDateandreleaseattribute values for the newVersionobject.Since JIRA version 7.0.1, this is deprecated on favour ofVersionManager.createVersion(String, java.util.Date, java.util.Date, String, Long, Long, boolean)which lets you specify thereleaseattribute value for the newVersionobject.since 7.4 no need for passing issueType if passing WorkflowNameThebulkLoadflag is no longer relevant. UseJiraPropertySetFactory.buildCachingDefaultPropertySet(String)instead. Since v6.2.These property sets can become stale if multiple instances are created with the same backingpropertySetdelegate and are also unsafe in a clustered environment. UseJiraPropertySetFactory.buildCachingDefaultPropertySet(String)orJiraPropertySetFactory.buildCachingPropertySet(String, Long)instead. Since v6.2.com.atlassian.jira.propertyset.JiraPropertySetFactory.buildCachingPropertySet(String, Long, boolean) ThebulkLoadflag is no longer relevant. UseJiraPropertySetFactory.buildCachingPropertySet(String, Long)instead. Since v6.2.the notion of "all the avatar sizes" is broken. We plan to eventually scale to any reasonable pixel size.This endpoint can cause serious performance issues and will be removed in Jira 9.0.UseVersionBeanFactory.createVersionBean(com.atlassian.jira.project.version.Version, boolean, boolean)instead. Since JIRA REST v6.5.1 (JIRA v6.1.1)UseVersionBeanFactory.createVersionBeans(Collection, boolean, boolean)instead. Since JIRA REST v6.5.1 (JIRA v6.1.1)Just assume all schemes are project association schemes.this class will be made immutable, create a new Scheme instead.this class will be made immutable, create a new Scheme instead.this class will be made immutable, create a new Scheme instead.this class will be made immutable, create a new Scheme instead.this class will be made immutable, create a new Scheme instead.this class will be made immutable, create a new Scheme instead.this class will be made immutable, create a new Scheme instead.UseSchemeManager.addDefaultSchemeToProject(com.atlassian.jira.project.Project)instead. Since v5.0.UseSchemeManager.addSchemeToProject(com.atlassian.jira.project.Project, Scheme)instead. Since v5.0.UseSchemeManager.copyScheme(Scheme)instead. Since v5.0.UseSchemeManager.createSchemeObject(String, String)instead. Since v5.0.UseSchemeManager.getDefaultSchemeObject()instead. Since v5.0.UseSchemeManager.getGroups(Long, com.atlassian.jira.project.Project)instead. Since v5.0.UseSchemeManager.getSchemeObject(Long)instead. Since v5.0.useSchemeManager.getSchemeObject(String)instead. Since 2010.useSchemeManager.getSchemeObjects(). Since 2010.UseSchemeManager.getSchemeFor(com.atlassian.jira.project.Project)instead. Since v5.0.UseSchemeManager.getUsers(Long, com.atlassian.jira.permission.PermissionContext)instead. Since 2006.UseSchemeManager.getEntities(org.ofbiz.core.entity.GenericValue, Long)andSchemeManager.deleteEntity(Long)instead. Since v5.0.UseSchemeManager.removeSchemesFromProject(com.atlassian.jira.project.Project)instead. Since v4.4.UseSchemeManager.updateScheme(Scheme)instead. Since v5.0.com.atlassian.jira.security.ApplicationRequiredPermissionManager.hasPermission(int, ApplicationUser) useGlobalPermissionManager.getGlobalPermission(GlobalPermissionKey)to get global permission by key. Eventually, we want to stop referring to Global Permission's by ID.UseGlobalPermissionManager.getGroupNamesWithPermission(com.atlassian.jira.permission.GlobalPermissionKey)instead. Since v6.2.5.UseGlobalPermissionManager.getGroupsWithPermission(com.atlassian.jira.permission.GlobalPermissionKey)instead. Since v6.2.5.UseGlobalPermissionManager.getPermissions(com.atlassian.jira.permission.GlobalPermissionKey)instead. Since v6.2.5.UseGlobalPermissionKeyinstead ofint. Since v6.2.5Since v7.0. Only retrieve the users you really need. SeeGroupPickerSearchServicesince 7.2.0.useGroupManager.getGroup(String)instead. Since 6.5Use one of the otherisUserInGroupmethods that takes a concrete user object instead. Since v6.4.8.UseDateTimeFormatterinstead. Since v5.0.UseJiraAuthenticationContext.getLoggedInUser(). Since v7.0UseRequestCacheFactoryinstead; it has safer semantics.UseRequestCacheFactoryinstead; it has safer semantics.UsePermissionManager.hasPermission(ProjectPermissionKey, Issue, ApplicationUser)instead. Since v6.3.UsePermissionManager.hasPermission(ProjectPermissionKey, Project, ApplicationUser)instead. Since v6.3.UsePermissionManager.hasPermission(ProjectPermissionKey, Project, ApplicationUser, boolean)instead. Since v6.3.UsePermissionManager.hasProjects(ProjectPermissionKey, ApplicationUser)instead. Since v6.3.Log in permission will be changing significantly in JIRA 7.0 ... if you are using this method, then you will need to watch out for announcements in 7.0 Developer upgrade guide. Since v6.2.5No longer used. Also you should be using GlobalPermissionKey now instead of int.This method is a shim. callGlobalPermissionManager.isGlobalPermission(int)instead.com.atlassian.jira.security.PublicAccessPermissionManager.hasPermission(int, Issue, ApplicationUser) UseProjectRoleManager.createProjectIdToProjectRolesMapWithGroups(ApplicationUser, Set<String>)instead. Since v9.10.Since 9.12. UseSecurityType.getUsers(PermissionContext, String, String, int)instead.Since 6.2UseServiceManager.addService(String, String, String)instead. Since v6.4.UseServiceManager.addService(String, Class, String, java.util.Map)instead. Since v6.4.UseServiceManager.addService(String, String, String)instead. Since v6.4.UseServiceManager.addService(String, String, String, java.util.Map)instead. Since v6.4.UseServiceManager.editService(Long, String, java.util.Map)instead. Since v6.4.UseServiceManager.editServiceByName(String, String, java.util.Map)instead. Since v6.4.v6.2 This is no longer used. Just callServiceManager.runNow(long)since v6.2 This is going away, it was always only meant for internal use.useServiceUtils.findIssueObjectInString(String)insteaduseServiceUtils.findIssueObjectsInString(String)insteaduseIssueManager.getIssueObject(String)insteadUseIssueManager.getIssueObject(String)instead. Since v6.1.UseSharedEntity.getOwner()instead. Since v6.0.The user name of the owner of the entity. Will always have permission to see it and see all shares.
This has been moved to the PortalPageManager and deprecated for SearchRequestManager. Since v5.2.use hasValidSharePermissions insteadUseContexts.builder()instead. Since v6.4.UseContexts.builder()instead. Since v6.4.Since 6.3.6 useContexts.percentageReporter(com.atlassian.jira.util.collect.Sized, TaskProgressSink, I18nHelper, Logger, String, String, String)for 6.3.6+ orContexts.builder()for 6.4+Since 6.3.6 use {@link #percentageReporter(com.atlassian.jira.util.collect.Sized, TaskProgressSink, I18nHelper, Logger, String, String, String, com.atlassian.johnson.event.Event), Level} in 6.3.6+ orContexts.builder()in 6.4+UseContexts.builder()instead. Since v6.4.UseContexts.builder()instead. Since v6.4.UseContexts.builder()instead. Since v6.4.These objects are flyweights so there is no longer any point in them being cached. This method no longer does anything. Since v6.2.UseUserPreferencesManager.getExtendedPreferences(ApplicationUser)instead. Since v6.0.Since v7.0. Only retrieve the users you really need. SeeUserSearchServiceUseBuildUtilsInfo.getCommitId()instead. Since v5.1.UseApplicationUser.getKey()orIdentifierUtils.toLowerCase(String). Since v6.0UseImmutableSortedMapdirectly instead. Since v6.1.UseImmutableSortedMapdirectly instead. Since v6.1.UseLists.newArrayList(Object[])instead. Since v5.0.UseLists.newArrayList(Object[])instead. Since v5.0.Buffering streams is actively harmful! See the class description as to why. UseIOUtil.copy(InputStream, OutputStream)instead.since v4.4. UseJiraDurationUtils.parseDuration(String location, Locale locale)instead.UseDurationFormatChangedinstead. Since 7.2.please useJiraEntityUtils.updateDependentEntitiesCheckId(org.ofbiz.core.entity.GenericValue, java.util.Collection, String, String)instead, as it compares ids rather thanGenericValuesUseIssueKey.from(String)instead. Since v6.1.UseIssueKey.from(String)instead. Since v6.1.UseIssueKey.from(String)instead. Since v6.1.UseIssueKey.from(String)instead. Since v6.1.The casing of this method is misleading; useJiraUtils.isSetUp()instead. Since v7.4.Since v6.4 usecom.atlassian.adapter.jackson.ObjectMapper#writeValueAsString(java.lang.Object)instead and properly escape output.to Use toLongMaybe instead, since v7.4.0UseDateTimeFormatterFactoryinstead. Since v5.2.UseDateTimeFormatterFactoryinstead. Since v5.2.since 7.2. UseProgressPageControl.wait(WebTester, String, String, String)instead.UseVelocityRequestContextFactory.setVelocityRequestContext(VelocityRequestContext)instead. Since v5.0.UseVelocityRequestContextFactory.setVelocityRequestContext(javax.servlet.http.HttpServletRequest)instead. Since v5.0.since 7.1 Storing information on theHttpSessionis not supported. Please move the functionality to the frontend or other type of storage. This class will be removed in 8.0.UseVelocityRequestContextFactory.setVelocityRequestContext(VelocityRequestContext)instead. Since v5.0.since 7.1 Storing information on the httpsession is obsoleted. Please move this functionality to the frontend or other type of storage.since 7.1 Storing information on the httpsession is obsoleted. Please move this functionality to the frontend or other type of storage.since 7.1 Storing information on the httpsession is obsoleted. Please move this functionality to the frontend or other type of storage.UseBulkWorkflowTransition.getDestinationStatusObject(WorkflowTransitionKey)instead. Since v7.0.UseBulkWorkflowTransition.getOriginStatusObject(WorkflowTransitionKey)instead. Since v7.0UseIssueCreationHelperBean.createFieldScreenRenderer(com.atlassian.jira.issue.Issue)instead. Since v6.2.Since 7.1. Storing information on the httpsession is obsoleted. Please move this functionality to the frontend or other type of storage. This method will be removed in 8.0.since 6.3 useTemporaryAttachmentsMonitor.clearEntriesForFormToken(String)instead.since 6.3 useTemporaryAttachmentsMonitor.getByFormToken(String)instead.UseFieldScreenRendererFactoryinstead. Since v5.0.UseFieldScreenRendererFactoryinstead. Since v5.0.Since 7.1. Storing information on the httpsession is obsoleted. Please move this functionality to the frontend or other type of storage. This method will be removed in 8.0.Since 7.1. Storing information on the httpsession is obsoleted. Please move this functionality to the frontend or other type of storage. This method will be removed in 8.0.Since 7.1. Storing information on the httpsession is obsoleted. Please move this functionality to the frontend or other type of storage. This method will be removed in 8.0.Since 7.1. Storing information on the httpsession is obsoleted. Please move this functionality to the frontend or other type of storage. This method will be removed in 8.0.Storing information on the httpsession is obsoleted. Please move this functionality to the frontend or other type of storage. This method will be removed in 8.0. Since 7.1Since 7.1. Storing information on the httpsession is obsoleted. Please move this functionality to the frontend or other type of storage. This method will be removed in 8.0.Since 7.1. Storing information on the httpsession is obsoleted. Please move this functionality to the frontend or other type of storage. This method will be removed in 8.0.Storing information on the httpsession is obsoleted. Please move this functionality to the frontend or other type of storage. This method will be removed in 8.0. Since 7.1UseConstantsManagerinstead. Since v6.0.UseConstantsManagerinstead. Since v6.0.UseJiraWebActionSupport.getLoggedInUser(). Since v7.0UseConstantsManagerinstead. Since v6.0.UseConstantsManagerinstead. Since v6.0.UseJiraWebActionSupport.getDateTimeFormatter()instead. Since v5.0.UseJiraWebActionSupport.hasGlobalPermission(com.atlassian.jira.permission.GlobalPermissionKey)instead. Since v6.4.UseJiraWebActionSupport.isUserExistsByName(String)orJiraWebActionSupport.isUserExistsByKey(String)instead, as appropriate. Since v6.0.since 5.1. UseJiraWebActionSupport.returnMsgToUser(String, String, MessageType, boolean, String)instead.useViewProjects.getProjectObjects()instead.callProject.getProjectLead()instead.Since 7.1. Storing this on the httpsession does not work for cloud. Storing information on the httpsession is obsoleted. Please move this functionality to the frontend or other type of storage. This method will be removed in 8.0.Since 7.1. Storing this on the httpsession does not work for cloud. Storing information on the httpsession is obsoleted. Please move this functionality to the frontend or other type of storage. This method will be removed in 8.0.UseBulkEditBean.getSingleProject()instead. Since v5.2.UseBulkEditBean.getProjectObjects()instead. Since v5.2.Since 7.1. Storing this on the httpsession does not work for cloud. Storing information on the httpsession is obsoleted. Please move this functionality to the frontend or other type of storage. This method will be removed in 8.0.Since 7.1. Storing this on the httpsession does not work for cloud. Storing information on the httpsession is obsoleted. Please move this functionality to the frontend or other type of storage. This method will be removed in 8.0.Since 7.1. Storing information on the httpsession is obsoleted. Please move this functionality to the frontend or other type of storage.UseBulkEditBean.getTargetStatusObject(com.atlassian.jira.issue.Issue)instead. Since v7.0Since 7.1. Storing this on the httpsession does not work for cloud. Storing information on the httpsession is obsoleted. Please move this functionality to the frontend or other type of storage. This method will be removed in 8.0.Since 7.1. Storing this on the httpsession does not work for cloud. Storing information on the httpsession is obsoleted. Please move this functionality to the frontend or other type of storage. This method will be removed in 8.0.Since 7.1. Storing this on the httpsession does not work for cloud. Storing information on the httpsession is obsoleted. Please move this functionality to the frontend or other type of storage. This method will be removed in 8.0.Since 7.1. Storing information on the httpsession is obsoleted. Please move this functionality to the frontend or other type of storage.UseBulkEditBean.setTargetProject(com.atlassian.jira.project.Project)instead. Since v5.2.Since 7.1. Storing information on the httpsession is obsoleted. Please move this functionality to the frontend or other type of storage.Since 7.1. Storing information on the httpsession is obsoleted. Please move this functionality to the frontend or other type of storage.Since 7.1. Storing information on the httpsession is obsoleted. Please move this functionality to the frontend or other type of storage.Since 6.3.8 useIssueTableWebComponent.asHtml(java.io.Writer, IssueTableLayoutBean, java.util.List, Pager, Long). It is inefficient in using memory as it uses a string writer.Since 6.3.8 useIssueTableWebComponent.asHtml(java.io.Writer, IssueTableLayoutBean, java.util.List, Pager, Long). It is inefficient in using memory as it uses a string writer.since 6.3.8 please useIssueTableWebComponent.asHtml(java.io.Writer, IssueTableLayoutBean, java.util.List, Pager, Long)and pass in the writer object.since 6.3.8 please useIssueTableWebComponent.asHtml(java.io.Writer, IssueTableLayoutBean, java.util.List, Pager, Long)and pass in the writer object.since 7.1 Storing information on the httpsession is obsoleted. Please move this functionality to the frontend or other type of storage. This method will be removed in 8.0.since 7.1 Storing information on the httpsession is obsoleted. Please move this functionality to the frontend or other type of storage. This method will be removed in 8.0.UseAuthorizationSupport.hasGlobalPermission(com.atlassian.jira.permission.GlobalPermissionKey)instead. Since v6.4.since v6.2.4: Inject an instance ofHelpUrlsto access JIRA's help.since 8.17.0. UseInternalServerErrorDataSource.appendFullMessageData(ImmutableMap.Builder, boolean, boolean)instead.since 8.17.0. UseInternalServerErrorDataSource.appendSimpleMessageData(ImmutableMap.Builder, boolean)instead.UseLocaleManager.getInstalledLocales()) instead. Since v4.2UseLocaleManager.getInstalledLocalesWithDefault(java.util.Locale, com.atlassian.jira.util.I18nHelper)) instead. Since v4.2Use {@link com.atlassian.jira.util.LocaleParser#parseLocale) instead. Since v4.2UseDays.daysBetween(org.joda.time.ReadablePartial, org.joda.time.ReadablePartial)instead. Since v4.4.UseDays.daysBetween(org.joda.time.ReadablePartial, org.joda.time.ReadablePartial)instead. Since v4.4.UseDateTimeFormatter.format(java.util.Date)instead. Since v4.4.UseDateTimeFormatter.format(java.util.Date)instead. Since v4.4.UseDateTimeFormatter.format(java.util.Date)instead. Since v4.4.UseDateTimeFormatter.format(java.util.Date)instead. Since v4.4.UseDateTimeFormatter.format(java.util.Date)instead. Since v4.4.UseDateTimeFormatter.format(java.util.Date)instead. Since v5.0.UseDateTimeFormatter.format(java.util.Date)instead. Since v5.0.UseDateTimeFormatter.format(java.util.Date)instead. Since v4.4.UseDateTimeFormatter.format(java.util.Date)instead. Since v5.0.UseDateTimeFormatter.format(java.util.Date)instead. Since v5.0.UseDateTimeFormatter.getFormatHint()instead. Since v4.4.UseDateTimeFormatter.format(java.util.Date)instead. Since v4.4.UseDateTimeFormatter.parse(String)instead. Since v5.0.UseDateTimeFormatter.parse(String)instead. Since v4.4.UseDateTimeFormatter.parse(String)instead. Since v4.4.UseDateTimeFormatter.parse(String)instead. Since v4.4.UseDateTimeFormatter.parse(String)instead. Since v5.0.UseDateTimeFormatterFactory.formatter()instead. Since v4.4.Use#createAttachment(webwork.multipart.MultiPartRequestWrapper, com.atlassian.crowd.embedded.api.User, com.atlassian.jira.issue.Issue, String, java.util.Map)instead. Since v5.0.This method doesn't have replacement as it is not needed anymore in the new API. Seeinstead. Since v6.4.useRestSupport.RestClient.getTarget(String, Map)insteadUseTextAssertions.assertTextSequence(String, String, String...)orTextAssertions.assertTextSequence(String, String[])instead usingHtmlPage.getCollapsedResponseText()as source of collapsed response text.UseTextAssertions.assertTextSequence(java.lang.String, java.lang.String, java.lang.String...)instead. Since v7.1.com.atlassian.jira.webtests.AbstractAtlassianWebTestCase.assertTextPresentBeforeText(String, String) Use {@link TextAssertions#assertTextSequence(java.lang.String, java.lang.String[])#} instead. Since v7.1.Use {@link TextAssertions#assertTextSequence(java.lang.String, java.lang.String[])#} instead. Since v7.1.UseForm.clickAnyButtonWithValue(String)instead.UseForm.clickButtonWithValue(String)instead.useHtmlPage.getCollapsedResponseText()insteadPlease useJIRAEnvironmentData.getWorkingDirectory(). This was renamed to avoid confusion with the "jira-home" functionality. Deprecated since v4.0UseAssertions.assertNodeByIdDoesNotExist(java.lang.String)instead. Since v7.1.UseAssertions.assertNodeByIdExists(java.lang.String)instead. Since v7.1.UseWebTester.assertRadioOptionValueNotPresent(String, String)useForm.selectOptionsByDisplayName(String, String[])instead.UseWorkflow.getLinkedStatusObjects()instead. Since v5.0.UseWorkflow.getLinkedStep(com.atlassian.jira.issue.status.Status)instead. Since v5.0.since v6.3since v6.3since v6.3UseJiraWorkflow.getLinkedStatusObjects()instead. Since v5.0.UseJiraWorkflow.getLinkedStatus(com.opensymphony.workflow.loader.StepDescriptor)instead. Since v7.0.UseJiraWorkflow.getLinkedStep(com.atlassian.jira.issue.status.Status)instead. Since v5.0.UseWorkflowFunctionUtils.getCallerUser(java.util.Map, java.util.Map)instead. Since v6.0.UseWorkflowFunctionUtils.getCallerUser(java.util.Map, java.util.Map)instead. Since v6.0.Since 5.1. This method should not be used directly by external developers as it is an operation that only makes sense in the context of a higher level operation in JIRA (i.e. project removal / changing the workflow scheme of a given project).Please use the API calls for these higher level operations instead.
UseWorkflowManager.copyWorkflow(com.atlassian.jira.user.ApplicationUser, String, String, JiraWorkflow)instead. Since v6.0.UseWorkflowManager.createDraftWorkflow(com.atlassian.jira.user.ApplicationUser, String)instead. Since v6.0.UseWorkflowManager.createWorkflow(com.atlassian.jira.user.ApplicationUser, JiraWorkflow)instead. Since v6.0.UseWorkflowManager.getWorkflow(com.atlassian.jira.issue.Issue)instead. Since v6.2.Since 5.0. UseWorkflowManager.getWorkflowsFromScheme(com.atlassian.jira.scheme.Scheme)instead.UseWorkflowManager.makeWorkflow(com.atlassian.jira.user.ApplicationUser)instead. Since v6.0.UseWorkflowManager.overwriteActiveWorkflow(com.atlassian.jira.user.ApplicationUser, String)instead. Since v6.0.UseWorkflowManager.updateWorkflow(com.atlassian.jira.user.ApplicationUser, JiraWorkflow)instead. Since v6.0.UseWorkflowProgressAware.getRemoteApplicationUser()instead. Since v6.0.Workflows have a String ID. Since v6.4.Workflows have a String ID. Since v6.4.Workflows have a String ID. Since v6.4.UseWorkflowTransitionUtil.getUserKey()instead. Since v6.0.UseWorkflowTransitionUtil.setUserkey(String)instead. Since v6.0.UseWorkflowTransitionUtilImpl.getRemoteApplicationUser()instead. Since v6.2.3.UseWorkflowTransitionUtilImpl.getUserKey()instead. Since v6.0.UseWorkflowTransitionUtilImpl.setUserkey(String)instead. Since v6.0.useBaseLicenseDetails.getSupportEntitlementNumber()insteadUseJiraLicenseHandler.addProductLicense(String, String)instead. Since 3.0.
-
Deprecated ConstructorsConstructorDescriptioncom.atlassian.jira.bc.dataimport.ExportCompletedEvent
(ApplicationUser, String, ServiceOutcome<Void>) UseSubTaskImpl(Long, com.atlassian.jira.issue.Issue, com.atlassian.jira.issue.Issue)instead. Since v5.0.Please useNode(String, NodeState, Long, String, Long, Long, String)instead.since 5.0.7since 6.1.1. UseAbstractRemoteIssueLinkEvent(com.atlassian.jira.issue.link.RemoteIssueLink)instead.since 6.1.1. UseRemoteIssueLinkCreateEvent(com.atlassian.jira.issue.link.RemoteIssueLink)instead.since 6.1.1. UseRemoteIssueLinkUICreateEvent(com.atlassian.jira.issue.link.RemoteIssueLink)instead.since 6.1.1. UseRemoteIssueLinkUIDeleteEvent(com.atlassian.jira.issue.link.RemoteIssueLink)instead.since 6.1.1. UseRemoteIssueLinkUpdateEvent(com.atlassian.jira.issue.link.RemoteIssueLink)instead.Please usePermissionSchemeDeletedEvent(Long, String). Since v6.2UseVersionDeleteEvent.VersionDeleteEventBuilderinstead.Pre-analytics constructor, event named "updateuserpreferences"; never whitelisted. Since 7.2.Please useWorkflowSchemeDeletedEvent(Long, String). Since v6.2com.atlassian.jira.functest.framework.navigation.IssueNavigationImpl(WebTester, JIRAEnvironmentData) JRADEV-14514 - The issues column has been removed from the filter listfieldConfigId and configurationSchemeId properties do not necessarily have to have equal values thus the former one should be explicitly specified when creating an instance of this class, just like the latter one. Objects created with this constructor may become the reason for a failed project import, see https://jira.atlassian.com/browse/JRASERVER-65734. Since v7.6.7UseProjectContext(Long, com.atlassian.jira.project.ProjectManager)instead. Since v6.4.UseProjectContext(Long, com.atlassian.jira.project.ProjectManager)instead. Since v6.4.UseProjectContext(Long, com.atlassian.jira.project.ProjectManager)instead. Since v6.4.UseAssigneeOption(String, String, String, String)instead. Since v5.0.Use {@link #DefaultUserBeanFactory(com.atlassian.jira.issue.fields.rest.json.beans.JiraBaseUrls, com.atlassian.jira.util.EmailFormatter, com.atlassian.jira.timezone.TimeZoneManager))}Use {@link #DefaultUserBeanFactory(com.atlassian.jira.issue.fields.rest.json.beans.JiraBaseUrls, com.atlassian.jira.util.EmailFormatter, com.atlassian.jira.timezone.TimeZoneManager))}since 8.12.1 useReindexAllSlowIndexersEvent(Iterable)UseSearchRequest(com.atlassian.query.Query, com.atlassian.jira.user.ApplicationUser, String, String)instead. Since v6.0.Build a SearchRequest with the provided attributes, this can be used if you want to create a SearchRequest that can be persisted.
UseSearchRequest(com.atlassian.query.Query, com.atlassian.jira.user.ApplicationUser, String, String, Long, long)instead. Since v6.0.Build a SearchRequest with the provided attributes.
since 8.9 useNumberEqualityQueryFactory(DoubleConverter)since 8.9 use {NumberRelationalQueryFactory(DoubleConverter)}This constructor is deprecated and will be removed in Jira 11.0. UseVersionSpecificRelationalOperatorQueryFactory(VersionResolver, Comparator, IndexInfoResolver)instead.Use the other constructor. Since 6.2.Use the other constructor. Since 6.0.UseNumberCustomFieldValidator(JqlOperandResolver, NumberIndexValueConverter, I18nHelper.BeanFactory)instead. Since v5.0.since 6.4.9UseUserIsAdminCondition(GlobalPermissionManager)instead. Since v7.1.UseJiraDurationUtils(TimeTrackingConfiguration, DurationFormatterProvider, EventPublisher)instead. Since v6.2.UseJiraDurationUtils(TimeTrackingConfiguration, DurationFormatterProvider, EventPublisher)instead. Since v7.2.#DaysDurationFormatter(BigDecimal, I18nHelper) is preferred now that we can fractional number of hours per dayUseAbstractPluggableTabPanelAction(PluginAccessor, UserPreferencesManager)}, which enables the user preferences manager to be injected.useI18nBean(java.util.Locale)insteadsince v6.2.4: Inject an instance ofHelpUrlsto access JIRA's help.since v6.2.4: Inject aHelpUrlsParserand use itsHelpUrlsParser.parse(java.util.Properties, java.util.Properties)method.since v6.2.4: Inject aHelpUrlsParserand use itsHelpUrlsParser.parse(java.util.Properties)method.useSearchSort(String, SortOrder)instead.in 9.9: use the other, complete constructor
-
Deprecated Enum ConstantsEnum ConstantDescriptionUse
ApplicationPropertiesService.getEditableAdvancedProperties()or the/rest/api/2/application-properties/advanced-settingsREST resource instead. Since v7.1.- Metric is not related to Instrumentation API and will be maintained within In-Products Diagnostics API.- Metric is not related to Instrumentation API and will be maintained within In-Products Diagnostics API.- Metric is not related to Instrumentation API and will be maintained within In-Products Diagnostics API.- Metric is not related to Instrumentation API and will be maintained within In-Products Diagnostics API.- Metric is not related to Instrumentation API and will be maintained within In-Products Diagnostics API.- Metric is not related to Instrumentation API and will be maintained within In-Products Diagnostics API.- Metric is not related to Instrumentation API and will be maintained within In-Products Diagnostics API.- Metric is not related to Instrumentation API and will be maintained within In-Products Diagnostics API.- Metric is not related to Instrumentation API and will be maintained within In-Products Diagnostics API.- Metric is not related to Instrumentation API and will be maintained within In-Products Diagnostics API.- Metric is not related to Instrumentation API and will be maintained within In-Products Diagnostics API.- Metric is not related to Instrumentation API and will be maintained within In-Products Diagnostics API.- Metric is not related to Instrumentation API and will be maintained within In-Products Diagnostics API.- Metric is not related to Instrumentation API and will be maintained within In-Products Diagnostics API.- Metric is not related to Instrumentation API and will be maintained within In-Products Diagnostics API.- Metric is not related to Instrumentation API and will be maintained within In-Products Diagnostics API.- Metric is not related to Instrumentation API and will be maintained within In-Products Diagnostics API.- Metric is not related to Instrumentation API and will be maintained within In-Products Diagnostics API.use theDateTimeFormatterFactoryand theDateTimeStyle.RELATIVE_WITHOUT_TIMEuse theDateTimeFormatterFactoryand theDateTimeStyle.RELATIVE_ALWAYS_WITH_TIMEuse theDateTimeFormatterFactoryand theDateTimeStyle.RELATIVE_WITH_TIME_ONLY
VersionSpecificRelationalOperatorQueryFactory(VersionResolver, Comparator, IndexInfoResolver)instead.