java.lang.Object | ||
↳ | com.atlassian.jira.plugin.webfragment.conditions.AbstractWebCondition | |
↳ | com.atlassian.jira.plugin.webfragment.conditions.AbstractIssueWebCondition |
![]()
CanAttachFileToIssueCondition,
CanConvertToIssueCondition,
CanConvertToSubTaskCondition,
CanManageAttachmentsCondition,
HasSubTasksAvailableCondition,
HasVotedForIssueCondition,
IsIssueAssignedToCurrentUserCondition,
IsIssueEditableCondition,
IsIssueReportedByCurrentUserCondition,
IsIssueUnresolvedCondition,
IsSubTaskCondition,
IsWatchingIssueCondition,
NoAttachmentsCondition
|
Clients of @PublicSpi
can expect
that programs compiled against a given version will remain binary compatible with later versions of the
@PublicSpi
as per each product's API policy (clients should refer to each product's API policy for
the exact guarantee -- usually binary compatibility is guaranteed at least across minor versions).
@PublicSpi
interfaces and classes are specifically designed to be implemented/extended by clients.
Hence, the guarantee of binary compatibility is different to that of @PublicApi
elements (if an element
is both @PublicApi
and @PublicSpi
, both guarantees apply).
Convenient abstraction for Conditions that are aware of JIRA's authentication and project- or issue-related contexts. These can be used in action configurations to guard conditionally displayed content.
An issue must be in the JiraHelper context params.
Public Constructors | |||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
Public Methods | |||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
Should we display this item for this issue?
|
[Expand]
Inherited Methods | |||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
![]() | |||||||||||||||||
![]() | |||||||||||||||||
![]() |
Should we display this item for this issue?
user | The current user |
---|---|
issue | The issue we are displaying against |
jiraHelper | The JiraHelper |