Jack Brickey Expert

Assuming you are an administrator and on Cloud then go to Jira settings > Apps > and search for X-ray. If you are on server it should be similar.

@Pahoua Hang, boards are simply visual filters. You need to create a new board for the project that you moved the issues to. Issue belong to projects not boards so the issues still exist it is simply that your old board’s filter is using the old project so you simply need to edits the filter from the old board and replace…

@GG, please provide screenshot for your sla and calendar so I can assess.

The number is not a concern. It just comes down to the likelyhood that the teams want to configure their workflows differently. You can always move a teams issues to new projects later as long as you have some field you can filter on to distinguish them from the rest.

I have not done this myself so my best recommendation is to search the Community and atlassian documentation for details. I know there are more than a few documents/threads on this. As best I recall from my readings, it would go something like this: * install JSD on your JSW instance * backup your JSD instance * restore…

ok. that is a default "Business Project" board you cannot configure that. Create your own kanban board using the appropriate filter, e.g. project = "Lead Tracking". You will need to select your profile as the "Location". Then on the sidebar of your project add a link to board.

that is absolutely the issue. one instance does not know about the other. I have never connected two instances so I'm not sure I can provide direct assistance. there are some threads about connecting two instances. I would recommend using the search box at the top of the page. FWIW, i think two instances creates…

@Thomas Deiler, man you have to love that right! :-) @jo astley, I can't say I have ever witnessed that and isn't the case in my instance so definitely work w/ Atlassian support.

btw...this really should be a different question since the original is specific to NG projects. but since we are already here...

Can you provide a screenshot of what you are seeing?

you could always add a login in to your site before users can access the widget. Otherwise, you might check the Marketplace for an addon app.

Ugh! you MUST change your workflow to clear the resolution anytime you reopen. If you do this then your issues should appear in the backlog. If they do not then you have something filtering them out. 

are you on Cloud? If so look at this to see if it could meet your need project > settings > widget it may be available on server as well. just not immediately sure.

your image is presenting something foreign to me. Can you tell me if you are on Cloud or Server? can you provide a full screen shot so I can figure out where you are at? In cloud you can do the following: click magnifying glass, click view all issues, delete the text in the search box and paste in what i recommended. In…

you look to be on a Server instance? Can you switch to "Advanced" query?

* who is in the "Developers1" group? * Do those listed have JSW application access? Obviously they will need this to collaborate. * are you logging in as one of those users or having them test? * you mention "if you try to access JSD link..." . What link, a JSD issue link? if they are redirected to the portal then they are…

@Megan Hicks, first let's keep the discussion in one thread by using the "Reply" rather than "Answer button. It is at times difficult to convey best practices in a thread. if I were viewing your instance I might better understand. With that said... If I have a number of separate projects/boards that ultimately I want to…

@Roman Joss, you might look at an automation addon like Automation for Jira. Below is a quick test example I just did. You will need to figure out what you could trigger on. I just chose Component here.

Warren's pic are for Server so if on server use that. if on cloud then follow the instructions i provided Jira settings > Products > Jira software

try this article - https://confluence.atlassian.com/jirasoftwarecloud/migrate-between-next-gen-and-classic-projects-957974933.html?_ga=2.219588569.1126327733.1544451210-984850702.1519156242

Me me me... classic, a bit quirky, fun, reasonably reliable...

I can’t say what is best. My opinion would depend on really understanding your environment, team, culture, processes. However, generally I stick with a single project if the issuetypes, workflows, permissions, screen schemes etc. are the same. Otherwise I split the project. Now with that said, if these are truly different…

It depends on how you differentiate them today? Is there any field that conveys this info? I mentioned the use of the “components” field. A board is simply a visual representation of a filter so for example... Artist Board: project = abc AND Components = “Artists” Dev Board: project = abc AND Components = “Developers”

@Marius Abalaru, I have edited out confidential info in you post given this is a public forum. Is there a reason that you have installed JSW on a different server? Ideally you should run JSW as an application on the existing instance.

I don’t believe this is available at this time. At least I have no run across it. I would recommend clicking the feedback and let Atlassian know.

Construct a JQL something like this... project = abc AND createdDate = 2019-01-30 change the operators and date as needed

@Marius Abalaru, You should be able to simply create a group (settings > user management > groups) call it JSD Colaborators or whatever you want. Then give the group browse and comment access in the project (project > project settings > permissions)

@Patrick McCarthy, see if this document helps using-parallel-sprints. The document is a bit dated. It should read - Jira settings > Products > Jira software

Do you own the board? The board owner should see board settings.

It is hard to say exactly how I would set things up based upon the info you have provided. However, I would think separate projects if the teams want to work independently of each other. However, if they are all working on a single ‘product’ then one or a few project would work using Components to define the areas. now…