Loading...

XML

Word

Printable

Details

Type: Suggestion
Resolution: Answered
Component/s: Classic - Board Configuration
Labels:
- affects-server

Feedback Policy:

Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

Description

We have built up a hierachy of issues types "Feature", "User Story" and "Story Task" - with custom coding for automatic issue links, status synchronization, custom field inheritance, effort accumulation and reporting. 2,000 users worldwide.

The feature "Simplified Workflows" (http://confluence.atlassian.com/display/GH/Using+GreenHopper+Simplified+Workflow) would break our complete process rules and reporting infrastructure. therefore we need to be sure, that GreenHopper remains fully functional and consistent without "Simplified Workflows".

The UI must not have any references to "Simplified Workflows" in this case.

Attachments

Issue Links

details

JSWCLOUD-6754 As an Atlassian (enterprise) customer I request that Rapid Board fulfills some MUST HAVE requirements

Closed

is related to

JSWCLOUD-6626 As a JIRA system admin I want to decide, if the GreenHopper UI supports Epics or not

Closed

relates to

JSWCLOUD-6892 As an Enterprise GreenHopper user I need to be assured that the act of a project admin enabling Simplified Workflows on a single project containing 200,000 issues will not adversely affect any users of the JIRA instance

Closed

JSWCLOUD-6893 As a JIRA Global Administrator I would like to undo the action of a project administrator who has enabled SImplified Workflows

Closed

Activity

People

Assignee:: Unassigned

Reporter:: rainer mueck

Votes:: 17 Vote for this issue

Watchers:: 16 Start watching this issue

Dates

Created:: 18/Nov/2012 11:19 AM

Updated:: 19/Sep/2019 6:11 AM

Resolved:: 28/May/2014 5:02 AM