Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id C4BA8200C5C for ; Thu, 20 Apr 2017 14:46:11 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id C36EF160BB1; Thu, 20 Apr 2017 12:46:11 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 205B9160B91 for ; Thu, 20 Apr 2017 14:46:10 +0200 (CEST) Received: (qmail 24849 invoked by uid 500); 20 Apr 2017 12:46:10 -0000 Mailing-List: contact issues-help@ambari.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@ambari.apache.org Delivered-To: mailing list issues@ambari.apache.org Received: (qmail 24839 invoked by uid 99); 20 Apr 2017 12:46:10 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd4-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 20 Apr 2017 12:46:10 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd4-us-west.apache.org (ASF Mail Server at spamd4-us-west.apache.org) with ESMTP id E8A12C28F9 for ; Thu, 20 Apr 2017 12:46:09 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd4-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -100.002 X-Spam-Level: X-Spam-Status: No, score=-100.002 tagged_above=-999 required=6.31 tests=[RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd4-us-west.apache.org [10.40.0.11]) (amavisd-new, port 10024) with ESMTP id zHWIFAOFEjWG for ; Thu, 20 Apr 2017 12:46:06 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTP id BA46C60DB8 for ; Thu, 20 Apr 2017 12:46:05 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id 44EB1E0041 for ; Thu, 20 Apr 2017 12:46:05 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 6F23E21B61 for ; Thu, 20 Apr 2017 12:46:04 +0000 (UTC) Date: Thu, 20 Apr 2017 12:46:04 +0000 (UTC) From: "Supreeth Sharma (JIRA)" To: issues@ambari.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (AMBARI-20729) Need way to explicitly ask for workflow name MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Thu, 20 Apr 2017 12:46:11 -0000 [ https://issues.apache.org/jira/browse/AMBARI-20729?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Supreeth Sharma updated AMBARI-20729: ------------------------------------- Attachment: AMBARI-20729.trunk.01.patch > 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)