How to markdown nested list items in Bitbucket?

I'm trying to see my markdown nested list items rendered with corresponding indentation when viewed in a browser live from the Bitbucket pages. But I can't figure out how it works even when using their examples (updated):

* Item 1
* Item 2
* Item 3
  * Item 3a
  * Item 3b
  * Item 3c

It ignores indentation for items 3a-c:

I want it to look like this (syntax works perfectly fine on SE and Github):

Their list in list example is particularly unacceptable:

1. Step 1
2. Step 2
3. Step 3
   * Item 3a
   * Item 3b
   * Item 3c

Here's a repo I set up just for this.

Solution 1:

Use 4 spaces.

# Unordered list

* Item 1
* Item 2
* Item 3
    * Item 3a
    * Item 3b
    * Item 3c

# Ordered list

1. Step 1
2. Step 2
3. Step 3
    1. Step 3.1
    2. Step 3.2
    3. Step 3.3

# List in list

1. Step 1
2. Step 2
3. Step 3
    * Item 3a
    * Item 3b
    * Item 3c

Here's a screenshot from that updated repo:

Thanks @Waylan, your comment was exactly right.

Solution 2:

Possibilities

• It is possible to nest a bulleted-unnumbered list into a higher numbered list.
• But in the bulleted-unnumbered list the automatically numbered list will not start: Its is not supported.
• To start a new numbered list after a bulleted-unnumbered one, put a piece of text between them, or a subtitle: A new numbered list cannot start just behind the bulleted: The interpreter will not start the numbering.

In practice

1. Dog
2. German Shepherd - with only a single space ahead. 2. Belgian Shepherd - max 4 spaces ahead.

• Number in front of a line interpreted as a "numbering bullet", so making the indentation. * ..and ignores the written digit: Places/generates its own, in compliance with the structure. * So it is OK to use only just "1" ones, to get your numbered list. * Or whatever integer number, even of more digits: The list numbering will continue by increment ++1. * However, the first item in the numbered list will be kept, so the first leading will usually be the number "1".
  1. Malinois - 5 spaces makes 3rd level already.
     1. MalinoisB - 5 spaces makes 3rd level already.
     2. Groenendael - 8 spaces makes 3rd level yet too.
     3. Tervuren - 9 spaces for 4th level - Intentionaly started by "55".
     4. TervurenB - numbered by "88", in the source code.

87. Cat
88. Siberian; a. SiberianA - problem reproduced: Letters (i.e. "a" here) not recognized by the interpreter as "numbering".

• No matter, that it is indented to its separated line in its source code: The indentation is ignored here. 2. Siamese
• a. so written manually as a workaround misusing bullets, unnumbered list.

Solution 3:

4 spaces do the trick even inside definition list:

Endpoint
: `/listAgencies`

Method
: `GET`

Arguments
:   * `level` - bla-bla.
    * `withDisabled` - should we include disabled `AGENT`s.
    * `userId` - bla-bla.

I am documenting API using BitBucket Wiki and Markdown proprietary extension for definition list is most pleasing (MD's table syntax is awful, imaging multiline and embedding requirements...).