[jira] [Resolved] (SYNCOPE-1093) Add some feedbacks when linking not existing groups/resources to existing user

[Andrea Patricelli (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SYNCOPE-1093?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andrea Patricelli resolved SYNCOPE-1093.

Resolution: Fixed

> Add some feedbacks when linking not existing groups/resources to existing user
> --
>
> Key: SYNCOPE-1093
> URL: https://issues.apache.org/jira/browse/SYNCOPE-1093
> Project: Syncope
>  Issue Type: Improvement
>  Components: enduser
>Reporter: Matteo Alessandroni
>Assignee: Andrea Patricelli
>Priority: Minor
> Fix For: 2.0.4, 2.1.0
>
>
> When using *syncope-enduser* to create or edit a User, it would be nice to 
> have a feedback when user tries to link a group or resource that does not 
> exist and block user from entering any group/resource when no 
> groups/resources are available in the system.
> For instance ("Group" test case):
> - I am in "Groups" tab and manually enter a not existing group name in 
> "Groups" input element;
> - Click "Next" and I'm on next tab;
> - Go back to "Groups" tab and the group I have entered is not there anymore.
> *Problem*: I have got no feedbacks about the situation and I have initially 
> thought my group was linked to my user.
> *Possible solution* ("Group" test case):
> * _Case 1_: there is a group at least:
> ** If user inserts a not existing group (he does not choose one from 
> dropdown) and clicks on "Next" button -->  show a message to warn that he 
> must choose a group from dropdown : Sample ;
> ** The group name he have entered will be removed from input element : Sample;
> ** If user inserts no groups, everything should work as usual.
> * _Case 2_: there are no groups:
> ** "Groups" input element should be disabled by default.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Assigned] (SYNCOPE-1093) Add some feedbacks when linking not existing groups/resources to existing user

[Andrea Patricelli (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SYNCOPE-1093?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andrea Patricelli reassigned SYNCOPE-1093:
--

Assignee: Andrea Patricelli

> Add some feedbacks when linking not existing groups/resources to existing user
> --
>
> Key: SYNCOPE-1093
> URL: https://issues.apache.org/jira/browse/SYNCOPE-1093
> Project: Syncope
>  Issue Type: Improvement
>  Components: enduser
>Reporter: Matteo Alessandroni
>Assignee: Andrea Patricelli
>Priority: Minor
> Fix For: 2.0.4, 2.1.0
>
>
> When using *syncope-enduser* to create or edit a User, it would be nice to 
> have a feedback when user tries to link a group or resource that does not 
> exist and block user from entering any group/resource when no 
> groups/resources are available in the system.
> For instance ("Group" test case):
> - I am in "Groups" tab and manually enter a not existing group name in 
> "Groups" input element;
> - Click "Next" and I'm on next tab;
> - Go back to "Groups" tab and the group I have entered is not there anymore.
> *Problem*: I have got no feedbacks about the situation and I have initially 
> thought my group was linked to my user.
> *Possible solution* ("Group" test case):
> * _Case 1_: there is a group at least:
> ** If user inserts a not existing group (he does not choose one from 
> dropdown) and clicks on "Next" button -->  show a message to warn that he 
> must choose a group from dropdown : Sample ;
> ** The group name he have entered will be removed from input element : Sample;
> ** If user inserts no groups, everything should work as usual.
> * _Case 2_: there are no groups:
> ** "Groups" input element should be disabled by default.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (SYNCOPE-1093) Add some feedbacks when linking not existing groups/resources to existing user

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/SYNCOPE-1093?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16052012#comment-16052012
 ] 

ASF subversion and git services commented on SYNCOPE-1093:
--

Commit 2f62dfb5af6e6818465bccad0314663e8233ff63 in syncope's branch 
refs/heads/2_0_X from [~skylark17]
[ https://git-wip-us.apache.org/repos/asf?p=syncope.git;h=2f62dfb ]

[SYNCOPE-1093] Disable select2search fields when no data is available


> Add some feedbacks when linking not existing groups/resources to existing user
> --
>
> Key: SYNCOPE-1093
> URL: https://issues.apache.org/jira/browse/SYNCOPE-1093
> Project: Syncope
>  Issue Type: Improvement
>  Components: enduser
>Reporter: Matteo Alessandroni
>Priority: Minor
> Fix For: 2.0.4, 2.1.0
>
>
> When using *syncope-enduser* to create or edit a User, it would be nice to 
> have a feedback when user tries to link a group or resource that does not 
> exist and block user from entering any group/resource when no 
> groups/resources are available in the system.
> For instance ("Group" test case):
> - I am in "Groups" tab and manually enter a not existing group name in 
> "Groups" input element;
> - Click "Next" and I'm on next tab;
> - Go back to "Groups" tab and the group I have entered is not there anymore.
> *Problem*: I have got no feedbacks about the situation and I have initially 
> thought my group was linked to my user.
> *Possible solution* ("Group" test case):
> * _Case 1_: there is a group at least:
> ** If user inserts a not existing group (he does not choose one from 
> dropdown) and clicks on "Next" button -->  show a message to warn that he 
> must choose a group from dropdown : Sample ;
> ** The group name he have entered will be removed from input element : Sample;
> ** If user inserts no groups, everything should work as usual.
> * _Case 2_: there are no groups:
> ** "Groups" input element should be disabled by default.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (SYNCOPE-1093) Add some feedbacks when linking not existing groups/resources to existing user

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/SYNCOPE-1093?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16052011#comment-16052011
 ] 

ASF subversion and git services commented on SYNCOPE-1093:
--

Commit eec50af7a26d87e88a5ce8b3f45e7b96d6bd8cb9 in syncope's branch 
refs/heads/master from [~skylark17]
[ https://git-wip-us.apache.org/repos/asf?p=syncope.git;h=eec50af ]

[SYNCOPE-1093] Disable select2search fields when no data is available. This 
closes #46


> Add some feedbacks when linking not existing groups/resources to existing user
> --
>
> Key: SYNCOPE-1093
> URL: https://issues.apache.org/jira/browse/SYNCOPE-1093
> Project: Syncope
>  Issue Type: Improvement
>  Components: enduser
>Reporter: Matteo Alessandroni
>Priority: Minor
> Fix For: 2.0.4, 2.1.0
>
>
> When using *syncope-enduser* to create or edit a User, it would be nice to 
> have a feedback when user tries to link a group or resource that does not 
> exist and block user from entering any group/resource when no 
> groups/resources are available in the system.
> For instance ("Group" test case):
> - I am in "Groups" tab and manually enter a not existing group name in 
> "Groups" input element;
> - Click "Next" and I'm on next tab;
> - Go back to "Groups" tab and the group I have entered is not there anymore.
> *Problem*: I have got no feedbacks about the situation and I have initially 
> thought my group was linked to my user.
> *Possible solution* ("Group" test case):
> * _Case 1_: there is a group at least:
> ** If user inserts a not existing group (he does not choose one from 
> dropdown) and clicks on "Next" button -->  show a message to warn that he 
> must choose a group from dropdown : Sample ;
> ** The group name he have entered will be removed from input element : Sample;
> ** If user inserts no groups, everything should work as usual.
> * _Case 2_: there are no groups:
> ** "Groups" input element should be disabled by default.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[GitHub] syncope pull request #46: Select2search fields improvements

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/syncope/pull/46


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Created] (SYNCOPE-1111) New any type

[JIRA]

Francesco Chicchiriccò created SYNCOPE-:
---

 Summary: New any type 
 Key: SYNCOPE-
 URL: https://issues.apache.org/jira/browse/SYNCOPE-
 Project: Syncope
  Issue Type: Bug
  Components: console
Affects Versions: 2.0.3
Reporter: Francesco Chicchiriccò
 Fix For: 2.0.4, 2.1.0


>From Admin Console:
# create new any type (say {{DEVICE}})
# go back to Realms: the new any type is not shown

After logging out and back in, the new any type is shown as expected.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Reopened] (SYNCOPE-1053) Show actual pending modifications during approval

[JIRA]

 [ 
https://issues.apache.org/jira/browse/SYNCOPE-1053?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Francesco Chicchiriccò reopened SYNCOPE-1053:
-

Reopening to fix an annoying issue: with the test users (which are available 
with standalone distribution and in embedded mode), a NPE is thrown; how to 
reproduce:
# log as {{puccini}} into Enduser UI and perform a change which requires 
approval
# log into Admin Console, claim the approval and edit, then view details

The NPE is raised at {{ApprovalDetails:45}} because {{formTO.getUserTO()}} is 
null: this can happen only with test users which were not effectively created 
via workflow.

A simple fix for this could be to disable the view button when 
{{formTO.getUserTO()}} is null.

> Show actual pending modifications during approval
> -
>
> Key: SYNCOPE-1053
> URL: https://issues.apache.org/jira/browse/SYNCOPE-1053
> Project: Syncope
>  Issue Type: Improvement
>  Components: console
>Reporter: Francesco Chicchiriccò
>Assignee: fabio martelli
> Fix For: 2.0.4, 2.1.0
>
>
> When performing approval via Admin Console, it is currently possible to look 
> at the data of the user being created / update.
> In case of update, however, it would be more useful to highlight somehow the 
> actual pending modifications.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[GitHub] syncope issue #46: Select2search fields improvements

[andrea-patricelli]

Github user andrea-patricelli commented on the issue:

https://github.com/apache/syncope/pull/46
  
@mat-ale perfect. Now you should squash the two commits of the pull request 
into a single commit then push changes to your repo in order to update the pull 
request. please refer to git doc, for example 
http://gitready.com/advanced/2009/02/10/squashing-commits-with-rebase.html


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] syncope issue #46: Select2search fields improvements

[mat-ale]

Github user mat-ale commented on the issue:

https://github.com/apache/syncope/pull/46
  
Hi @andrea-patricelli. 
As requested, I have just sent the ICLA to Apache.
Thanks,
Regards.


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] syncope issue #46: Select2search fields improvements

[andrea-patricelli]

Github user andrea-patricelli commented on the issue:

https://github.com/apache/syncope/pull/46
  
Hi @mat-ale ! In order to contribute you need first to sign and send ICLA 
to Apache. Then we can continue to merge this pull request.

BR


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Commented] (SYNCOPE-1093) Add some feedbacks when linking not existing groups/resources to existing user

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/SYNCOPE-1093?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16051729#comment-16051729
 ] 

ASF GitHub Bot commented on SYNCOPE-1093:
-

GitHub user mat-ale opened a pull request:

https://github.com/apache/syncope/pull/46

Select2search fields improvements

This solves the improvement 
[#SYNCOPE-1093](https://issues.apache.org/jira/browse/SYNCOPE-1093), but no 
feedback was added for issue "Case 1" in order not to add too much complexity 
to a customizable enduser.



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/mat-ale/syncope select2searchFeedbacks

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/syncope/pull/46.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #46


commit e91cf09308c27b6a4a42c788fe63d2b82c605437
Author: Matteo Alessandroni 
Date:   2017-06-15T14:56:06Z

Disable select2search fields when no data is available

Signed-off-by: Matteo Alessandroni 

commit a6deffc387eb8c9577cd53a23599792984cb6cd9
Author: Matteo Alessandroni 
Date:   2017-06-16T08:35:28Z

currently selected groups are removed when user choose a different realm

Signed-off-by: Matteo Alessandroni 




> Add some feedbacks when linking not existing groups/resources to existing user
> --
>
> Key: SYNCOPE-1093
> URL: https://issues.apache.org/jira/browse/SYNCOPE-1093
> Project: Syncope
>  Issue Type: Improvement
>  Components: enduser
>Reporter: Matteo Alessandroni
>Priority: Minor
> Fix For: 2.0.4, 2.1.0
>
>
> When using *syncope-enduser* to create or edit a User, it would be nice to 
> have a feedback when user tries to link a group or resource that does not 
> exist and block user from entering any group/resource when no 
> groups/resources are available in the system.
> For instance ("Group" test case):
> - I am in "Groups" tab and manually enter a not existing group name in 
> "Groups" input element;
> - Click "Next" and I'm on next tab;
> - Go back to "Groups" tab and the group I have entered is not there anymore.
> *Problem*: I have got no feedbacks about the situation and I have initially 
> thought my group was linked to my user.
> *Possible solution* ("Group" test case):
> * _Case 1_: there is a group at least:
> ** If user inserts a not existing group (he does not choose one from 
> dropdown) and clicks on "Next" button -->  show a message to warn that he 
> must choose a group from dropdown : Sample ;
> ** The group name he have entered will be removed from input element : Sample;
> ** If user inserts no groups, everything should work as usual.
> * _Case 2_: there are no groups:
> ** "Groups" input element should be disabled by default.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[GitHub] syncope pull request #46: Select2search fields improvements

[mat-ale]

GitHub user mat-ale opened a pull request:

https://github.com/apache/syncope/pull/46

Select2search fields improvements

This solves the improvement 
[#SYNCOPE-1093](https://issues.apache.org/jira/browse/SYNCOPE-1093), but no 
feedback was added for issue "Case 1" in order not to add too much complexity 
to a customizable enduser.



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/mat-ale/syncope select2searchFeedbacks

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/syncope/pull/46.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #46


commit e91cf09308c27b6a4a42c788fe63d2b82c605437
Author: Matteo Alessandroni 
Date:   2017-06-15T14:56:06Z

Disable select2search fields when no data is available

Signed-off-by: Matteo Alessandroni 

commit a6deffc387eb8c9577cd53a23599792984cb6cd9
Author: Matteo Alessandroni 
Date:   2017-06-16T08:35:28Z

currently selected groups are removed when user choose a different realm

Signed-off-by: Matteo Alessandroni 




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Resolved] (SYNCOPE-1053) Show actual pending modifications during approval

[fabio martelli (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SYNCOPE-1053?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

fabio martelli resolved SYNCOPE-1053.
-
Resolution: Fixed

> Show actual pending modifications during approval
> -
>
> Key: SYNCOPE-1053
> URL: https://issues.apache.org/jira/browse/SYNCOPE-1053
> Project: Syncope
>  Issue Type: Improvement
>  Components: console
>Reporter: Francesco Chicchiriccò
>Assignee: fabio martelli
> Fix For: 2.0.4, 2.1.0
>
>
> When performing approval via Admin Console, it is currently possible to look 
> at the data of the user being created / update.
> In case of update, however, it would be more useful to highlight somehow the 
> actual pending modifications.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (SYNCOPE-1053) Show actual pending modifications during approval

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/SYNCOPE-1053?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16051532#comment-16051532
 ] 

ASF subversion and git services commented on SYNCOPE-1053:
--

Commit c679035d94013250ffa3a328be71b6885447cece in syncope's branch 
refs/heads/master from [~fmartelli]
[ https://git-wip-us.apache.org/repos/asf?p=syncope.git;h=c679035 ]

[SYNCOPE-1053] Handling previous object and new object during approval


> Show actual pending modifications during approval
> -
>
> Key: SYNCOPE-1053
> URL: https://issues.apache.org/jira/browse/SYNCOPE-1053
> Project: Syncope
>  Issue Type: Improvement
>  Components: console
>Reporter: Francesco Chicchiriccò
>Assignee: fabio martelli
> Fix For: 2.0.4, 2.1.0
>
>
> When performing approval via Admin Console, it is currently possible to look 
> at the data of the user being created / update.
> In case of update, however, it would be more useful to highlight somehow the 
> actual pending modifications.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (SYNCOPE-1053) Show actual pending modifications during approval

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/SYNCOPE-1053?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16051529#comment-16051529
 ] 

ASF subversion and git services commented on SYNCOPE-1053:
--

Commit 78b68bf4b84a1ad79d4ba246f4030e02344cbbfb in syncope's branch 
refs/heads/2_0_X from [~fmartelli]
[ https://git-wip-us.apache.org/repos/asf?p=syncope.git;h=78b68bf ]

[SYNCOPE-1053] Handling previous object and new object during approval


> Show actual pending modifications during approval
> -
>
> Key: SYNCOPE-1053
> URL: https://issues.apache.org/jira/browse/SYNCOPE-1053
> Project: Syncope
>  Issue Type: Improvement
>  Components: console
>Reporter: Francesco Chicchiriccò
>Assignee: fabio martelli
> Fix For: 2.0.4, 2.1.0
>
>
> When performing approval via Admin Console, it is currently possible to look 
> at the data of the user being created / update.
> In case of update, however, it would be more useful to highlight somehow the 
> actual pending modifications.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)