{"action":"created","issue":{"url":"https://api.github.com/repos/open-keychain/open-keychain/issues/1450","labels_url":"https://api.github.com/repos/open-keychain/open-keychain/issues/1450/labels{/name}","comments_url":"https://api.github.com/repos/open-keychain/open-keychain/issues/1450/comments","events_url":"https://api.github.com/repos/open-keychain/open-keychain/issues/1450/events","html_url":"https://github.com/open-keychain/open-keychain/pull/1450","id":95561008,"number":1450,"title":"secret key status activity","user":{"login":"Valodim","id":27813,"avatar_url":"https://avatars.githubusercontent.com/u/27813?v=3","gravatar_id":"","url":"https://api.github.com/users/Valodim","html_url":"https://github.com/Valodim","followers_url":"https://api.github.com/users/Valodim/followers","following_url":"https://api.github.com/users/Valodim/following{/other_user}","gists_url":"https://api.github.com/users/Valodim/gists{/gist_id}","starred_url":"https://api.github.com/users/Valodim/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/Valodim/subscriptions","organizations_url":"https://api.github.com/users/Valodim/orgs","repos_url":"https://api.github.com/users/Valodim/repos","events_url":"https://api.github.com/users/Valodim/events{/privacy}","received_events_url":"https://api.github.com/users/Valodim/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":7,"created_at":"2015-07-17T00:54:38Z","updated_at":"2015-08-02T17:16:49Z","closed_at":null,"pull_request":{"url":"https://api.github.com/repos/open-keychain/open-keychain/pulls/1450","html_url":"https://github.com/open-keychain/open-keychain/pull/1450","diff_url":"https://github.com/open-keychain/open-keychain/pull/1450.diff","patch_url":"https://github.com/open-keychain/open-keychain/pull/1450.patch"},"body":"I started working on what I mentioned in #1449. The idea is that a user can see what operations are available for a (secret) key, but not in terms of subkeys. This translates into a simple activity which displays a status each for confirm, sign and decrypt.\r\n\r\nI covered all obvious cases, but currently only the subkey status itself is considered and not others, like when the entire key is revoked. I reckon there is also some room for improvement in the way of understandable wording and design.\r\n\r\nThe activity is currently accessible via the context menu, but I also thought about displaying it right after the user imports a secret key, which will hopefully help for scenarios like #1436 where the user isn't entirely aware of what operations a secret key can or cannot do.\r\n\r\nscreenshot from the fragment, it looks a little better in action but I can't make a very good screenshot at the moment:\r\n![](http://valodim.stratum0.net/layout-2015-07-16-215801.png)"},"comment":{"url":"https://api.github.com/repos/open-keychain/open-keychain/issues/comments/127046758","html_url":"https://github.com/open-keychain/open-keychain/pull/1450#issuecomment-127046758","issue_url":"https://api.github.com/repos/open-keychain/open-keychain/issues/1450","id":127046758,"user":{"login":"dschuermann","id":321888,"avatar_url":"https://avatars.githubusercontent.com/u/321888?v=3","gravatar_id":"","url":"https://api.github.com/users/dschuermann","html_url":"https://github.com/dschuermann","followers_url":"https://api.github.com/users/dschuermann/followers","following_url":"https://api.github.com/users/dschuermann/following{/other_user}","gists_url":"https://api.github.com/users/dschuermann/gists{/gist_id}","starred_url":"https://api.github.com/users/dschuermann/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/dschuermann/subscriptions","organizations_url":"https://api.github.com/users/dschuermann/orgs","repos_url":"https://api.github.com/users/dschuermann/repos","events_url":"https://api.github.com/users/dschuermann/events{/privacy}","received_events_url":"https://api.github.com/users/dschuermann/received_events","type":"User","site_admin":false},"created_at":"2015-08-02T17:16:49Z","updated_at":"2015-08-02T17:16:49Z","body":"I like really like the new design!\r\n* As you said in your initial comment, it should consider the revocation/expiry status of the master key.\r\n* The menu item should be removed\r\n\r\nLong term thoughts:\r\nWe can introduce buttons to guide the user to the right action, like extending the expiry"}}