Bug 1029547 - Comment not used when deleting an asset
Summary: Comment not used when deleting an asset
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: JBoss BRMS Platform 6
Classification: Retired
Component: Business Central
Version: 6.0.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: ---
Assignee: manstis
QA Contact: Zuzana Krejčová
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-11-12 15:09 UTC by Zuzana Krejčová
Modified: 2016-08-01 01:08 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-11-25 14:47:17 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
git log for deleted file ("Dummy rule.drl") (109.99 KB, image/png)
2013-11-25 14:47 UTC, manstis
no flags Details
Re-created asset ("Dummy rule.drl") showing delete comment in history (140.25 KB, image/png)
2013-11-25 14:48 UTC, manstis
no flags Details

Description Zuzana Krejčová 2013-11-12 15:09:35 UTC
Description of problem:
When deleting an asset, the 'Check in comment' the user is prompted for is never used, even when filled in.
If you delete an asset and fill in 'No longer necessary.' as the comment, the commit message in the underlying git will read 'delete {/<project>/<path>/<package>/<file>}' anyway.
The same is visible if you recreate the asset and look into the Version history.


Version-Release number of selected component (if applicable):
BPMS 6.0 ER4

Comment 1 manstis 2013-11-25 14:47:17 UTC
Using the latest codebase (master/.Final community) I cannot replicate this bug.

Deleting a file through the UI leads to the attached git log. Furthermore re-creating the same asset leads to the attached history in the UI.

Comment 2 manstis 2013-11-25 14:47:53 UTC
Created attachment 828713 [details]
git log for deleted file ("Dummy rule.drl")

Comment 3 manstis 2013-11-25 14:48:33 UTC
Created attachment 828714 [details]
Re-created asset ("Dummy rule.drl") showing delete comment in history


Note You need to log in before you can comment on or make changes to this bug.