This is my current solution to this Joke of a problem: 

• Create New Project (in order for the Filter to be set up)
• Delete the newly created Board
• Make a copy of my Template Board
• Rename the new Board
• Change Saved Filter of the new board to the one that was originally created.
• Change the Workflow scheme to use my default one in Admin Settings > Workflow Schemes
• Delete the workflow in Admin Settings > Workflow

It makes me really nervous that features like this are not addressed within 6 years. 

Thanks Joseph. I figured out something similar myself. you might consider posting your tip on https://community.atlassian.com/t5/Jira-questions/How-can-I-copy-a-scrum-board-to-another-project/qaq-p/123059 as well.

Agreed that this is pretty ridiculous. 

The best workaround I've found is just to copy an existing board then change the filter to point to the new project.  It's annoying but saves a lot of time recreating the whole thing.

This is my actual procedure (I create a temporary board to force Jira to automatically create the filter I need):

1. Open the project that needs a board.
2. Click Create board select board from an existing project.  Name it similar to the final desired board name, but not exact. example: "MyProject2 board" when I want my final board to be named "MyProject2".
3. Click Create board.
4. Open an existing board that should be used as the template for example: "MyProject1".  (found under Boards > View All boards)
5. Click Board > Copy.
6. The copied board should open.  Make some changes:
   1. Rename the board to "MyProject2" (the desired final board name).
   2. Click on Saved Filter.  Select the filter that was automatically created earlier.  for example: "Filter for MyProject2 board"
   3. Click Back to Board.
7. Click Boards > View All Boards.
   1. Locate the temporary board created earlier "MyProject2 board"
   2. Click the ... button and click Delete.

The more bizarre part is this request was created ALMOST SIX YEARS AGO, and as we do have the possibility to save templates for other stuff, this should be a no-brainer to implement.

/facepalm

Can't believe what I read here ...

EVERYBODY starting to seriously use the boards recognizes instantly, that this very basic feature is missing. Why does Atlassian not?

Seeing issues like this are making me not want to continue with the trial. 

This is our fault. Companies keep using Atlassian / JIRA like it is awesome while it's absurdly expensive and lacks a lot of things, so they just don't care to fix / implement useful stuff.

The same is happening with Source Tree and perpetual bugs that never get fixed but they keep changing / adding other stuff that no one asked for.

Way to go Atlassian.

Lolz

Still not resolved?! Coming up on the 5yr mark. 

I like these comments. Atlassian time to work now.

Hi.

I am another person who would like this feature. Thanks! 

If there were a "Like" button I would click it for the comment above!

In November 2012 I could not believe that this very basic feature was missing and I opened this request.

4.5 years later and users still have to beg for it ...

Atlassian, this is a tragedy. You treat your customers very badly.

Have you lately read https://www.atlassian.com/company/values ? Seems to be pretty much outdated

Pretty amazed that this hasn't been done yet.  This would save a lot of time and frustration for my customers that setup boards.  I am internal support for my org, and every time I go to visit with JIRA users the first thing I do is take a look at their board and it is almost always configured wrong.  Please include a method to have different template types.

Would like this as well and I'm surprised this is not a feature yet! That should be one of the basics!

I would love to see this implemented.  Having to configure the board columns each time a new project is created is a huge pain.  We have some boards with 10-20 columns.

This needs to be fixed.  I've got a dozen boards that each should behave identically, but are not.  I think on a similar issue Atlassian indicated this was working as desired as each board is intended to be unique.  There may be cases where that is desired, but that certainly does not meet our needs.

I can't believe that after FOUR YEARS such a basic (and very important) feature is still not implemented.

We have templates / schemes for a lot of things (Screens, Workflows, Fields, Permissions) yet BOARDS that every project needs we need to configure everytime we open a project.

My God...

I still can't believe they simply closed my request JSW-6754 - As an Atlassian (enterprise) customer I request that Rapid Board (now: JIRA Agile) fulfills some MUST HAVE requirements

We're still sitting on good old GreenHopper - what a shame.

Four years later .. any update on this?

This still hasn't been resolved?

This is a necessary feature, mocking a faux "template" by using the board copy feature is a convoluted timesink.

I'm with @csanchez1 on this one.

We've set up a department standard for JIRA Agile boards for things like card colors. Right now when we create a new board we copy it from an existing board.

However, if we ever change our scheme – at times we do as we're evolving our processes – we'd rather not have to go through a huge number of boards and individually update them. We'd rather have a scheme attached to all boards where we can make a single change and voila! all of the boards are updated.

Other than making the changes via SQL, is there a feature or add-on which would allow me to set up a JIRA Agile board scheme?

tj5, we see this as a valid Suggestion however we cannot provide any guidance at this time as to when, or if, we'll be implementing it.

As noted above the current workaround is to copy a new board from one with the desired configuration. After creation the board can be associated with a different Saved Filter as required.

Regards,
Martin
JIRA Agile

Two years later .. any update on this?

Here are similar / related needs, I believe, in my words:

We have several teams using their own Projects / Boards, which contain / show different content, but have (or should have...) the same characteristics / design.

Is it possible to create Project / Board templates:

• To base any new Project / Board instances on, and

• Such that when a template is changed, all existing / already / previously created instances are updated as well?

No. When I copy the board, it initially has the same filter as the original. However, I change that right away once the board is copied. If I use a custom filter, I save it prior to copying the board so I have it ready when I create the new one. Just make sure you rename the board and the filter in the new one.

Dave, are you not getting the issue that Matt Doar mentioned about it only having one same filter for the copied boards then?

I have resorted to calling a single board Scrum Template and copying it every time a new project is created. After the project is created, I rename the board and adjust the filter for the appropriate project. It is an effective work around but not the best solution.

Hi Shaun,

Any update on when this feature might be added? We have just started to look at the Rapid boards and this was pretty much the first feature we look for as using them without it will take us quiet some time of repetitive configuration for all the boards we need which are 95% the same.

Thanks.

Copy Board seems to make you use the same filter. Changing the filter in one board then messes up the other board, I think?

To me, there is a special pain that I have to re-do the quick filters for each board, especially the "Hide Done Issues" Filter. The pre-defined filters in the classic board were a good help to get started... If I could do a "board template" as addressed in this ticket, I could work around the regularly missing filters.

Hi Everyone,

Thanks so much for your votes and comments on this feature request, we wanted to provide an update on the status.

We know there are features missing from the new Scrum and Kanban boards. This feature represents one that we will explore further in the future. At this point in time we cannot provide any guidance on when, or if, it will be addressed.

Just like any Agile team we have ordered the backlog based upon what we believe provides the greatest value to our customers. There are now over 10,000 customers worldwide so we try to find the right balance between the varied needs of this large, and growing, group. It is not an easy task. Thankfully we have many passionate customers that are able to provide feedback to help drive our vision and order the backlog - thank you!

Thanks for your patience, we hope that our open approach to feature requests and backlog ordering allows you to see where we are headed.

Cheers,
Shaun Clowes
GreenHopper Product Manager