[
https://issues.apache.org/jira/browse/AMBARI-20729?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15978664#comment-15978664
]
Hudson commented on AMBARI-20729:
---------------------------------
SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #7333 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/7333/])
AMBARI-20729.Need way to explicitly ask for workflow name(Supreeth
(venkatasairam.lanka:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=b66d4b17e9fa03e1117b954ab41ff8bf9d6c18f6])
* (edit)
contrib/views/wfmanager/src/main/resources/ui/app/components/coord-config.js
* (edit)
contrib/views/wfmanager/src/main/resources/ui/app/components/bundle-config.js
> Need way to explicitly ask for workflow name
> ---------------------------------------------
>
> Key: AMBARI-20729
> URL: https://issues.apache.org/jira/browse/AMBARI-20729
> Project: Ambari
> Issue Type: Bug
> Components: ambari-views
> Affects Versions: 2.5.0
> Reporter: Supreeth Sharma
> Assignee: venkat
> Priority: Critical
> Labels: WFD, WFM
> Fix For: 2.5.1
>
> Attachments: AMBARI-20729.trunk.01.patch, AMBARI-20729-trunk.patch
>
>
> This is a ask from lot of users where they get confused between workflow name
> and workflow xml file name.
> Since workflow manager is auto populating workflow name, usually forgets to
> enter this manually.
> And once he saves the workflow at specific path, he expects the file name to
> be workflow name.
> This behaviour will also damage the user experience in project manager view.
> To avoid this ambiguity, workflow manager should explicitly ask for workflow
> name.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
