Jack Brickey Expert

i think the magic here depends on how one determines "real developer". If your team logs time then that is a reasonable approach but, as you pointed out is flawed, if you wanted something more definitive then you could add a custom user picker field that was required to be set by the developer when they move to in progress…

@Susan Hauth _Jira Queen_ , did u see the article I referenced. I ran across this the other day but I don't have server so cannot confirm it but would expect that since Atlassian documents it would work....that whole trust thing. ;-)

brining it back into the one thread here... So the fundamental principal of NG is to allow "anyone" to create and manage their own project w/o needing an admin. This will not change. If you want configurable permissions you should use Classic. if you are an admin and don't want to allow NG then you should disable this…

when you create the project you can select open/limited/private. does that not meet your needs?

If you are on server it is possible beginning 3.15 see this article. However, that isn’t available in cloud from what I have seen 

Fair question @[deleted] . TBH I have wondered why this was the case in the past too but never really dug in to get an answer as I just excepted it as the way the code worked. I have pinged other champions to see if they have a better answer to chime in here.

editing in new UI - the "edit" has been deprecated. all editing is done directly on the screen vs. bringing up a new modal. board name - if you are talking about a kanban or scrum board then you still click on the ellipses and go into board settings and general

no Austin this round. :-(

i would go to settings > user management filter on Service Desk access and then go into each user that does not need access and uncheck Service Desk access. 

Understand but I’m not sure I can really help you at this point. You might want to chat with Insight to see how they product might I trip with your current ticketing system. 

I guess my question is why have you found that JSD is the wrong application? I don’t use insight as yet but plan to test the cloud beta when it arrives and I have always viewed it to be an extension of my JSD. You certainly could move all existing issue out of JSD into a Core project. 

I am also getting underway opening up JSD for external customers as well. In one case at least I really don’t want the customers to have another portal so I’m looking at us8 g the Widget feature and embed it into an existing portal they use. Now this doesn’t have the benefit of viewing open requests. On thing you could do…

In cloud there is a Create linked issue. No admins are not agents.

You create whatever columns you want and you map the statuses into those columns. For example you could have a column per status if you liked so in you’re case 11 columns (map done and close in the last column). Or you could combine say Elab with New, ready for dev with open, etc. the columns are just containers to display…

so, i did a bit more research and found this document pointing to Miscellaneous workflow extensions. you might have a look at that. still it is a paid addon. maybe there is another way. but no time to dig further at the moment. 

hmmm, i may be mistaken. i surprised that you indicate it used to work. let me have a closer look.

yes but as i said there may be some clean up. i recall doing this a long time ago. for example you may find that you need to do it in steps, e.g. * move epic, or just create a new one in the new project * move stories then in the new project bulk edit and add the new epic link * i might suggest you add a temp label to all…

JSD issues can only be assigned to a JSD agent for the project in question. You can Create a linked issue in the JSW project. 

replace your Epic id w/ abc-123 above in the two locations and see if that works for you. do this in the advanced issue search screen.

correct. "you" cannot change someone else's name only they can by going to id.atlassian.com. unless of course you have their login info. :-)

you should create a jql to get the list where you want it, e.g. issuekey = abc-123 or epiclink = abc-123 then use bulk move to move all issue to the new project. there may be a bit of clean up but it should be relatively quick w/ bulk move

JSD does not have any native SMS capabilities. There are options in the Marketplace

You will need an addon for that to automate this. Have a look at Marketplace...some suggestions to consider: Scriptrunner, Power Scripts, Automation for Jira.

that is not currently available in NG. I checked the 'public NG roadmap' and saw no reference to this. However, that page hasn't been updated lately AFAIK. You might click the feedback button in your instance as Atlassian is interested in NG feedback.

Well, while they have not placed OPS out there for purchase yet (still beta and free) I'm quite sure it will be completely independent. You will pay per user for each and every tool: Jira, Confluence, OPS, JSD, OPSGenie, etc....

use the two-dimensional gadget on the Dashboard.

are you asking to search for attachment? AFAIK you will need an addon for that, e.g. Search Attachments. Disclaimer, I have no experience w/ the aforementioned addon so be sure to trial it and others.

actually, I don't really need/want the ability to treat sub-tasks independent of stories across sprints. while I don't mind if they provide a means of doing this I would hope it is configurable because I wan't to run sprints at a story level. sub-tasks are just a way to breakdown my story into a to-do list. that said, I…

there are a lot of existing threads in the Community discussing this. Some are to the right under Related Content. here is what many of us do.... * JSD issue is opened * JSD Agent determines the issue requires development * JSD Agent transitions the issue into a 'development' status * JSD Agent Creates linked issue in the…

Hi Grace, I'm not sure i have following you here. It seems that maybe your expectations are that by moving an issue from backlog to a sprint would result in any linked issues also being added to the sprint automatically. Do I have this right? To be clear, just because an issue is linked to another does not mean it will…