Why different URLs to access Team-managed Board sprint and Company-managed Active Sprint

[YY Brother]

Hi,

Anyone knows the reason why the differnece?

1.URL to access sprint of a team-managed project is: 

https://{{sitename}}.atlassian.net/jira/software/projects/{{projectkey}}/boards/1

2.URL to access sprint of a company-managed project is:

https://{{sitename}}.atlassian.net/jira/software/c/projects/{{projectkey}}/boards/1

Does the letter c mean company-managed? 😊

Thanks,

YY Bro

[Mykenna Cepek · Accepted solution]

I can't say for sure, but here's my plausible reasoning (as a former web and software developer):

There are likely two separate front-end codebases for UI/UX/rendering for TMPs vs CMPs (and of course they share a lot of middle- and back-end code). Allowing the high-level URL handlers to differentiate this likely eliminates the need for decoding that at lower levels.

Since CMPs came first, the default would have been that all URLs go to the code that knows how to do CMPs. When TMPs came along, using the same URL would require the CMP code to do a lookup to figure out that the project/board was for a TMP, then redirect to the different codebase that handles TMPs. That redirect and extra lookup likely impacted performance, so they found a way to "push it up the stack".

[YY Brother]

Hi @Mykenna Cepek 

Thanks for your reply. I‘ve consulted Atlassian teams and got the result that I need to change the codes of my Jira Cloud App accordingly.

• URL to access sprint of a team-managed project is: 

  https://{{sitename}}.atlassian.net/jira/software/projects/{{projectkey}}/boards/1

• URL to access sprint of a company-managed project is:

  https://{{sitename}}.atlassian.net/jira/software/c/projects/{{projectkey}}/boards/1

YY Bro

[Mykenna Cepek]

Right. That's the same thing as in your original post. But the question you asked was "why is there this difference"? Thanks for accepting my answer!