Bug 1007825 - Build & Deploy should automatically save changes
Summary: Build & Deploy should automatically save changes
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss BRMS Platform 6
Classification: Retired
Component: Business Central
Version: 6.0.0
Hardware: Unspecified
OS: Unspecified
medium
low
Target Milestone: ER5
: 6.0.0
Assignee: Jan
QA Contact: Zuzana Krejčová
URL:
Whiteboard:
Depends On:
Blocks: bpms6_ux, brms6_ux
TreeView+ depends on / blocked
 
Reported: 2013-09-13 11:59 UTC by Zuzana Krejčová
Modified: 2016-08-01 01:08 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-08-06 20:17:54 UTC
Type: Enhancement
Embargoed:

Attachments (Terms of Use)

Description Zuzana Krejčová 2013-09-13 11:59:05 UTC 
Description of problem:
It would be nice if clicking Build & Deploy in the Project Editor also automatically saved changes made there.

Example use case: User wants to deploy an updated version of a project. He updates the project, raises the project version to mark this and hits Build & Deploy right away. The change to the project version is saved automatically.
Comment 1 Prakash Aradhya 2013-09-17 02:18:02 UTC 
Internal Whiteboard: Beta Blocker → Blocker
Not critical for Beta, but need to address for GA
Comment 2 Edson Tirelli 2013-09-30 22:25:24 UTC 
Probably should ask for user confirmation to save or discard the changes.
Comment 6 Jan 2013-10-09 15:37:40 UTC 
Implemented as per Comment 2; i.e. the user is asked if he wants to save the project pom before building. Also added a popup notification after saving, similar to the one that appears at the top of the screen after building.
Comment 7 Zuzana Krejčová 2013-10-15 08:22:15 UTC 
It either does not work or didn't get into the product for ER4. I see no change from ER3.
Comment 8 Edson Tirelli 2013-10-15 13:21:43 UTC 
Based on the date this issue was fixed (2013-Oct-09), this would was not included in the ER4 build (2013-Sep-27th + specific cherry-picked commits).

I am setting this back to MODIFIED and it will be available in the next build (ER5?).
Comment 9 Zuzana Krejčová 2013-12-09 17:47:02 UTC 
Verified with ER5.
Note You need to log in before you can comment on or make changes to this bug.