[JBoss JIRA] (DROOLS-2423) [DMN Designer] Clear command caches context entries
by Jozef Marko (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2423?page=com.atlassian.jira.plugi... ]
Jozef Marko updated DROOLS-2423:
--------------------------------
Description:
This issue was spotted during review of DROOLS-2392, however relation is not probable between both.
If user clears the top level context entry and then select same context entry exactly the same context entry will appear. There should appear context entry with default values.
h2. Acceptance test
# check scenario described in [PR comments|https://github.com/kiegroup/kie-wb-common/pull/1548]
# check scenario from DROOLS-2424
# Steps to reproduce fixed - Clear the context entry at depth:
-- 0 (/)
-- 1 (/)
-- 2
-- 3
was:
This issue was spotted during review of DROOLS-2392, however relation is not probable between both.
If user clears the top level context entry and then select same context entry exactly the same context entry will appear. There should appear context entry with default values.
h2. Acceptance test
# check scenario described in [PR comments|https://github.com/kiegroup/kie-wb-common/pull/1548]
# check scenario from DROOLS-2424
# Steps to reproduce fixed - Clear the context entry at depth:
-- 0 (/)
-- 1
-- 2
-- 3
> [DMN Designer] Clear command caches context entries
> ---------------------------------------------------
>
> Key: DROOLS-2423
> URL: https://issues.jboss.org/browse/DROOLS-2423
> Project: Drools
> Issue Type: Bug
> Components: DMN Editor
> Affects Versions: 7.8.0.Final
> Reporter: Jozef Marko
> Assignee: Michael Anstis
> Priority: Minor
> Attachments: Screenshot from 2018-03-27 11-31-01.png, Screenshot from 2018-03-27 11-31-34.png, Screenshot from 2018-03-27 11-32-52.png
>
>
> This issue was spotted during review of DROOLS-2392, however relation is not probable between both.
> If user clears the top level context entry and then select same context entry exactly the same context entry will appear. There should appear context entry with default values.
> h2. Acceptance test
> # check scenario described in [PR comments|https://github.com/kiegroup/kie-wb-common/pull/1548]
> # check scenario from DROOLS-2424
> # Steps to reproduce fixed - Clear the context entry at depth:
> -- 0 (/)
> -- 1 (/)
> -- 2
> -- 3
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 6 months
[JBoss JIRA] (DROOLS-2423) [DMN Designer] Clear command caches context entries
by Jozef Marko (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2423?page=com.atlassian.jira.plugi... ]
Jozef Marko updated DROOLS-2423:
--------------------------------
Description:
This issue was spotted during review of DROOLS-2392, however relation is not probable between both.
If user clears the top level context entry and then select same context entry exactly the same context entry will appear. There should appear context entry with default values.
h2. Acceptance test
# check scenario described in [PR comments|https://github.com/kiegroup/kie-wb-common/pull/1548]
# check scenario from DROOLS-2424
# Steps to reproduce fixed - Clear the context entry at depth:
-- 0 (/)
-- 1
-- 2
-- 3
was:
This issue was spotted during review of DROOLS-2392, however relation is not probable between both.
If user clears the top level context entry and then select same context entry exactly the same context entry will appear. There should appear context entry with default values.
h2. Acceptance test
# check scenario described in [PR comments|https://github.com/kiegroup/kie-wb-common/pull/1548]
# check scenario from DROOLS-2424
# Steps to reproduce fixed - Clear the context entry at depth:
-- 1
-- 2
-- 3
> [DMN Designer] Clear command caches context entries
> ---------------------------------------------------
>
> Key: DROOLS-2423
> URL: https://issues.jboss.org/browse/DROOLS-2423
> Project: Drools
> Issue Type: Bug
> Components: DMN Editor
> Affects Versions: 7.8.0.Final
> Reporter: Jozef Marko
> Assignee: Michael Anstis
> Priority: Minor
> Attachments: Screenshot from 2018-03-27 11-31-01.png, Screenshot from 2018-03-27 11-31-34.png, Screenshot from 2018-03-27 11-32-52.png
>
>
> This issue was spotted during review of DROOLS-2392, however relation is not probable between both.
> If user clears the top level context entry and then select same context entry exactly the same context entry will appear. There should appear context entry with default values.
> h2. Acceptance test
> # check scenario described in [PR comments|https://github.com/kiegroup/kie-wb-common/pull/1548]
> # check scenario from DROOLS-2424
> # Steps to reproduce fixed - Clear the context entry at depth:
> -- 0 (/)
> -- 1
> -- 2
> -- 3
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 6 months
[JBoss JIRA] (DROOLS-2423) [DMN Designer] Clear command caches context entries
by Jozef Marko (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2423?page=com.atlassian.jira.plugi... ]
Jozef Marko updated DROOLS-2423:
--------------------------------
Description:
This issue was spotted during review of DROOLS-2392, however relation is not probable between both.
If user clears the top level context entry and then select same context entry exactly the same context entry will appear. There should appear context entry with default values.
h2. Acceptance test
# check scenario described in [PR comments|https://github.com/kiegroup/kie-wb-common/pull/1548]
# check scenario from DROOLS-2424
# Steps to reproduce fixed - Clear the context entry at depth:
-- 1
-- 2
-- 3
was:
This issue was spotted during review of DROOLS-2392, however relation is not probable between both.
If user clears the top level context entry and then select same context entry exactly the same context entry will appear. There should appear context entry with default values.
h2. Acceptance test
# check scenario described in [PR comments|https://github.com/kiegroup/kie-wb-common/pull/1548]
# check scenario from DROOLS-2424
# TO DO
> [DMN Designer] Clear command caches context entries
> ---------------------------------------------------
>
> Key: DROOLS-2423
> URL: https://issues.jboss.org/browse/DROOLS-2423
> Project: Drools
> Issue Type: Bug
> Components: DMN Editor
> Affects Versions: 7.8.0.Final
> Reporter: Jozef Marko
> Assignee: Michael Anstis
> Priority: Minor
> Attachments: Screenshot from 2018-03-27 11-31-01.png, Screenshot from 2018-03-27 11-31-34.png, Screenshot from 2018-03-27 11-32-52.png
>
>
> This issue was spotted during review of DROOLS-2392, however relation is not probable between both.
> If user clears the top level context entry and then select same context entry exactly the same context entry will appear. There should appear context entry with default values.
> h2. Acceptance test
> # check scenario described in [PR comments|https://github.com/kiegroup/kie-wb-common/pull/1548]
> # check scenario from DROOLS-2424
> # Steps to reproduce fixed - Clear the context entry at depth:
> -- 1
> -- 2
> -- 3
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 6 months
[JBoss JIRA] (DROOLS-2436) [DMN Designer] Always open the same diagram
by Jozef Marko (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2436?page=com.atlassian.jira.plugi... ]
Jozef Marko updated DROOLS-2436:
--------------------------------
Description:
User is unable to open two different diagrams.
h2. Acceptance test
# Steps to reproduce fixed (/)
# Steps to reproduce fixed, do the last step in multiple browser sessions (/)
was:
User is unable to open two different diagrams.
h2. Acceptance test
# Steps to reproduce fixed
# Steps to reproduce fixed, do the last step in multiple browser sessions
> [DMN Designer] Always open the same diagram
> -------------------------------------------
>
> Key: DROOLS-2436
> URL: https://issues.jboss.org/browse/DROOLS-2436
> Project: Drools
> Issue Type: Bug
> Components: DMN Editor, Stunner
> Affects Versions: 7.8.0.Final
> Reporter: Jozef Marko
> Assignee: Roger Martínez
> Priority: Blocker
>
> User is unable to open two different diagrams.
> h2. Acceptance test
> # Steps to reproduce fixed (/)
> # Steps to reproduce fixed, do the last step in multiple browser sessions (/)
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 6 months
[JBoss JIRA] (WFLY-5793) Allow selective CI builds
by Radoslav Husar (JIRA)
[ https://issues.jboss.org/browse/WFLY-5793?page=com.atlassian.jira.plugin.... ]
Radoslav Husar edited comment on WFLY-5793 at 4/3/18 3:36 AM:
--------------------------------------------------------------
The update to this is that we now manage documentation within the wildfly repo in master branch, so any updates to the docs here do not need to run the whole CI -- probably only some sort of 'doc lint'. So the time saving cost here is *huge*.
Though, PRs that are also changing code but in subsequent updates only update documentation, the CI can't tell those apart and will have to run the whole suite again -- this is a disadvantage to having documentation as part of project source repo.
was (Author: rhusar):
The update to this is that we now manage documentation within the wildfly repo in master branch, so any updates to the docs here do not need to run the whole CI -- problably only some sort of 'doc lint'. Though, PRs that are also changing code but in subsequent updates only update documentation, the CI can't tell those apart and will have to run the whole suite again -- this is a disadvantage to having documentation as part of project source repo.
> Allow selective CI builds
> -------------------------
>
> Key: WFLY-5793
> URL: https://issues.jboss.org/browse/WFLY-5793
> Project: WildFly
> Issue Type: Task
> Reporter: Ryan Emerson
> Assignee: Ken Wills
> Priority: Optional
>
> Currently the testsuite is ran against all PRs regardless of which files are being changed. This is waste of energy/resources when commits only contain changes that do not effect code (e.g. when updating README.md).
> A possible solution would be for a blacklist to be created, which lists the file types which can be safely ignored by CI when a PR only contains changes to files of the listed file types.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 6 months
[JBoss JIRA] (WFLY-5793) Allow selective CI builds
by Radoslav Husar (JIRA)
[ https://issues.jboss.org/browse/WFLY-5793?page=com.atlassian.jira.plugin.... ]
Radoslav Husar edited comment on WFLY-5793 at 4/3/18 3:36 AM:
--------------------------------------------------------------
The update to this is that we now manage documentation within the wildfly repo in master branch, so any updates to the docs here do not need to run the whole CI -- probably only some sort of 'doc lint'. So the machine time saving cost here is huge.
Though, PRs that are also changing code but in subsequent updates only update documentation, the CI can't tell those apart and will have to run the whole suite again -- this is a disadvantage to having documentation as part of project source repo.
was (Author: rhusar):
The update to this is that we now manage documentation within the wildfly repo in master branch, so any updates to the docs here do not need to run the whole CI -- probably only some sort of 'doc lint'. So the time saving cost here is *huge*.
Though, PRs that are also changing code but in subsequent updates only update documentation, the CI can't tell those apart and will have to run the whole suite again -- this is a disadvantage to having documentation as part of project source repo.
> Allow selective CI builds
> -------------------------
>
> Key: WFLY-5793
> URL: https://issues.jboss.org/browse/WFLY-5793
> Project: WildFly
> Issue Type: Task
> Reporter: Ryan Emerson
> Assignee: Ken Wills
> Priority: Optional
>
> Currently the testsuite is ran against all PRs regardless of which files are being changed. This is waste of energy/resources when commits only contain changes that do not effect code (e.g. when updating README.md).
> A possible solution would be for a blacklist to be created, which lists the file types which can be safely ignored by CI when a PR only contains changes to files of the listed file types.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 6 months
[JBoss JIRA] (WFLY-5793) Allow selective CI builds
by Radoslav Husar (JIRA)
[ https://issues.jboss.org/browse/WFLY-5793?page=com.atlassian.jira.plugin.... ]
Radoslav Husar commented on WFLY-5793:
--------------------------------------
The update to this is that we now manage documentation within the wildfly repo in master branch, so any updates to the docs here do not need to run the whole CI -- problably only some sort of 'doc lint'. Though, PRs that are also changing code but in subsequent updates only update documentation, the CI can't tell those apart and will have to run the whole suite again -- this is a disadvantage to having documentation as part of project source repo.
> Allow selective CI builds
> -------------------------
>
> Key: WFLY-5793
> URL: https://issues.jboss.org/browse/WFLY-5793
> Project: WildFly
> Issue Type: Task
> Reporter: Ryan Emerson
> Assignee: Ken Wills
> Priority: Optional
>
> Currently the testsuite is ran against all PRs regardless of which files are being changed. This is waste of energy/resources when commits only contain changes that do not effect code (e.g. when updating README.md).
> A possible solution would be for a blacklist to be created, which lists the file types which can be safely ignored by CI when a PR only contains changes to files of the listed file types.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 6 months