tag:blogger.com,1999:blog-7079343994945292124.comments2023-05-25T07:54:00.478-04:00John Anastasio's BlogJohn Anastasiohttp://www.blogger.com/profile/11550788001868134035noreply@blogger.comBlogger34125tag:blogger.com,1999:blog-7079343994945292124.post-22239552768566471132018-08-17T04:03:42.667-04:002018-08-17T04:03:42.667-04:00Thanks. I helped me a lot.Thanks. I helped me a lot.Saradhinoreply@blogger.comtag:blogger.com,1999:blog-7079343994945292124.post-38811261029853918292018-01-03T16:57:42.562-05:002018-01-03T16:57:42.562-05:00This is a great workaround, but when you save to f...This is a great workaround, but when you save to file it doesn't save the headers. Is there a trick for that?<br />Thanks!Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-7079343994945292124.post-22878593979796893782016-10-13T17:34:00.184-04:002016-10-13T17:34:00.184-04:00Two thumbs up for finding this needle in a Hay Sta...Two thumbs up for finding this needle in a Hay Stack!MLJoinerhttps://www.blogger.com/profile/00622587585758007114noreply@blogger.comtag:blogger.com,1999:blog-7079343994945292124.post-90549788503049490632015-12-08T11:31:02.420-05:002015-12-08T11:31:02.420-05:00updated jdbc driver: https://www.microsoft.com/en...updated jdbc driver: https://www.microsoft.com/en-US/download/details.aspx?id=11774John Anastasiohttps://www.blogger.com/profile/03645547642105114260noreply@blogger.comtag:blogger.com,1999:blog-7079343994945292124.post-55121248182600304382015-11-04T10:33:35.870-05:002015-11-04T10:33:35.870-05:00Thanks! Would have taken forever for me to figure ...Thanks! Would have taken forever for me to figure out and this is the only thread I could find on this.Anonymoushttps://www.blogger.com/profile/06087435339008853754noreply@blogger.comtag:blogger.com,1999:blog-7079343994945292124.post-88107614405201514572015-01-22T18:22:40.633-05:002015-01-22T18:22:40.633-05:00You may have just missed step 3. Make sure to set ...You may have just missed step 3. Make sure to set your roles for the jira project. Keep in mind your developers can only access the service desk jira project, and not the actual service desk that the agents use. Also check that the users/user groups you set for each role have the permissions you want, which you can find Under JIRA administration, projects, select project, permissions. But in this case you probably want to add your developers to the Collaborator role.<br /><br />Additionally in the same permission area on the top right corner is a "permission helper", which should help you identify any constraints on a users permissions if you get stuck again.John Anastasiohttps://www.blogger.com/profile/11550788001868134035noreply@blogger.comtag:blogger.com,1999:blog-7079343994945292124.post-79891849191577810412015-01-22T02:59:25.327-05:002015-01-22T02:59:25.327-05:00thanx john. seems not to work by me: the service d...thanx john. seems not to work by me: the service desk addon always override the permissions prevent the developer to work/logwork on the issue.Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-7079343994945292124.post-34876464948599147982015-01-21T14:06:14.163-05:002015-01-21T14:06:14.163-05:00- You can have as many Service Desk's as you l...- You can have as many Service Desk's as you like. Each time you create a service desk it also create a Jira Project, unless you choose a Jira Project that already exists. In my case I have just 1 Service Desk, and 1 related Service Desk Jira Project. <br />- Yes you can have two Service Desks running with the add on, associated to two different projects.<br />- Yes you can move the issue to another project in your system. It can be a service desk project or not, doesn't matter.<br />- Yes developers can absolutely log their work, hence the reason for the work around.John Anastasiohttps://www.blogger.com/profile/11550788001868134035noreply@blogger.comtag:blogger.com,1999:blog-7079343994945292124.post-42058152019988918262015-01-21T11:10:31.788-05:002015-01-21T11:10:31.788-05:00how did you in this case avoid the default service...how did you in this case avoid the default servicedesk permissions override ?Anonymoushttps://www.blogger.com/profile/07808344774963498403noreply@blogger.comtag:blogger.com,1999:blog-7079343994945292124.post-52196587835575197322015-01-18T06:05:58.276-05:002015-01-18T06:05:58.276-05:00thank you for the workaround, sounds good.
- you h...thank you for the workaround, sounds good.<br />- you have 2 projects: a) "Service Desk" b) "Service Desk Jira Project". correct ?<br />- are both projects running with the "Jira Service Desk Add On" or only a) ?<br />- stay the issues unique or you have to move/clone them between a) and b) ?<br />- can developers still log their work ?<br />thank you for the clarification, julienAnonymousnoreply@blogger.comtag:blogger.com,1999:blog-7079343994945292124.post-68200938044612885202014-12-10T19:46:10.476-05:002014-12-10T19:46:10.476-05:00Yes it solves the work on issues problem. You will...Yes it solves the work on issues problem. You will have the actual "Service Desk" which the agents will have access to and a "Service Desk Jira Project" which the developers will have access to. Step 3 is where you provide developers access to the jira project and not the agents. The agents wouldn't have access to Jira, and the developers wouldn't have access to the service desk process and queues... as it should be. The agents can then assign developers to work on the issues, without them also being agents. The developers would then use the "Service Desk Jira project" as they would any other Jira project, with the addition that they can also comment both internally and externally to the customer. John Anastasiohttps://www.blogger.com/profile/11550788001868134035noreply@blogger.comtag:blogger.com,1999:blog-7079343994945292124.post-18244513073928306632014-12-10T05:33:09.056-05:002014-12-10T05:33:09.056-05:00Can you elaborate on that? I have the problem that...Can you elaborate on that? I have the problem that the devs need to be able to log work on an issue. Thus, they need to have the permission for "work on issues". I didn't try your workaround yet, but does it solve the "work on issues" problem?Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-7079343994945292124.post-64773896899803743402014-12-02T13:07:47.679-05:002014-12-02T13:07:47.679-05:00This work around allows you to assign service desk...This work around allows you to assign service desk issues to jira users where they can then work on, comment, and resolve those issues/tasks. This keeps the working support or dev roles and the customer success roles separate. Only the Agents can progress the issues/tasks back and forth between queues, distribute/manage the assignment, owning and driving successful resolution, and ultimately be the customer facing liaison.John Anastasiohttps://www.blogger.com/profile/11550788001868134035noreply@blogger.comtag:blogger.com,1999:blog-7079343994945292124.post-89202783812155238712014-12-02T10:05:19.982-05:002014-12-02T10:05:19.982-05:00This workaround is only for 'assign'. But ...This workaround is only for 'assign'. But you still cant work on issue unless you are 'agent'. Correct?Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-7079343994945292124.post-85730505974801217682013-09-26T12:26:27.736-04:002013-09-26T12:26:27.736-04:00This worked perfectly. Thank you for your clear di...This worked perfectly. Thank you for your clear directions!Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-7079343994945292124.post-89177085813527031032013-09-07T17:06:40.821-04:002013-09-07T17:06:40.821-04:00Thanks from Turkey:)Thanks from Turkey:)Anonymoushttps://www.blogger.com/profile/05943862915597834290noreply@blogger.comtag:blogger.com,1999:blog-7079343994945292124.post-50232345267168306372013-04-25T03:09:08.716-04:002013-04-25T03:09:08.716-04:00eyvallah hacı :)eyvallah hacı :)Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-7079343994945292124.post-2767701965959958482013-04-08T11:54:24.928-04:002013-04-08T11:54:24.928-04:00Or % characters, due to an Azure bug
http://blogs...Or % characters, due to an Azure bug<br /><br />http://blogs.msdn.com/b/windowsazurestorage/archive/2012/05/28/partitionkey-or-rowkey-containing-the-percent-character-causes-some-windows-azure-tables-apis-to-fail.aspxmattyboyhttps://www.blogger.com/profile/10929937237720909344noreply@blogger.comtag:blogger.com,1999:blog-7079343994945292124.post-51882046783267759352012-12-06T19:15:28.853-05:002012-12-06T19:15:28.853-05:00Looks like either your path is wrong in your cloud...Looks like either your path is wrong in your cloud .csproj project file or your build server may just be missing the targets file completely.John Anastasiohttps://www.blogger.com/profile/11550788001868134035noreply@blogger.comtag:blogger.com,1999:blog-7079343994945292124.post-61832518407090068952012-12-06T19:14:56.783-05:002012-12-06T19:14:56.783-05:00This comment has been removed by the author.John Anastasiohttps://www.blogger.com/profile/11550788001868134035noreply@blogger.comtag:blogger.com,1999:blog-7079343994945292124.post-37527135041584320982012-12-03T09:44:08.919-05:002012-12-03T09:44:08.919-05:00I have windows azure project with sdk 1.8 and i am...I have windows azure project with sdk 1.8 and i am able to run it on my local machine but when i check in to TFS, check in is successful but building is not successful<br /><br />The imported project "C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\v11.0\Windows Azure Tools\1.8\Microsoft.WindowsAzure.targets" was not found. <br /><br /><br />Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-7079343994945292124.post-82354378623779145922012-11-21T21:37:54.260-05:002012-11-21T21:37:54.260-05:00Dude... you are awesome. Thank you so freaking mu...Dude... you are awesome. Thank you so freaking much.JTtheGeekhttps://www.blogger.com/profile/02227292127506989206noreply@blogger.comtag:blogger.com,1999:blog-7079343994945292124.post-5211204477502847522012-10-26T02:13:24.848-04:002012-10-26T02:13:24.848-04:00Thanks I was too able to reload the project. Very ...Thanks I was too able to reload the project. Very usefull article. :)Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-7079343994945292124.post-31849214239077944002012-10-17T05:38:49.821-04:002012-10-17T05:38:49.821-04:00Thanks, this article was really helpful!Thanks, this article was really helpful!robaczekhttps://www.blogger.com/profile/10953562369142995057noreply@blogger.comtag:blogger.com,1999:blog-7079343994945292124.post-56741183054624843252012-07-30T15:38:23.644-04:002012-07-30T15:38:23.644-04:00John,
Thanks for posting this. It got me most of...John,<br /><br />Thanks for posting this. It got me most of the way through the process. The only thing I would add is that if you get an error message about not being able to establish a connection (or alternatively, an error message about not being able to close the connection) download and run sysinternals to see what port SQL Server is using. It might not be using the default port. It might be using another port altogether.<br /><br />Thanks again!Anonymousnoreply@blogger.com