Nic Brough -Adaptavist- Expert

Yes, that's exactly what sprint estimates are for - estimating the entire story for a multi-skilled team.

Nothing to apologize for! I thought you were shouting to show us an example!

Where is this, and where do we sign up?

Jira does not add story points from sub-tasks up into their parent issues because it breaks your reporting. Sub-tasks are a part of their parent story, not a separate entity and, most importantly, they are not items you commit to in a sprint. As they are not sprint items, they do not have sprint estimates. Their sprint…

>The only thing the user can do is adding/deleting a status via the board. Yes, that's editing the workflow. The point of simplified workflows is enabling the board owner to edit the workflow. But you don't want them editing the transitions, a simplified workflow is very simple and not intended to allow the users to break…

Yes

You get the content of the page, and update it with your new data. That's what an edit or update is.

Yes, your edit is deleting the original content. To add to the page, add your content, don't delete.

Sorry, but it does work like that. But there is a misunderstanding - Pramodh is talking about the extended admin route to editing workflows, whereas I'm talking about Simplified workflows.

I am not sure what you are trying to do here. Adding to a page IS an update. Add and edit are the same process. Just because you are not removing anything when you add to a page does not mean there is a different action.

Nope. Mojang are using a server/dc instance of Jira, not Cloud. The account is for Mojang systems, not an Atlassian account. I happen to know that through simply having seen this a load before, but @MysticWither gave us a great problem report by including the URL for the Jira they are trying to get into as well They can't…

You have to give them board admin rights as well.

"Adding to a page" is "updating a page". It does not delete anything, it adds a new version of the page with the new content.

Welcome to the Atlassian Community! You will need to contact the administrators of Mojang's Jira, we (the Community and Atlassian) have no access to their systems.

No, this is not an Atlassian problem.

Start by reading through https://confluence.atlassian.com/jirakb/troubleshoot-a-jira-server-startup-failed-error-394464512.html

That would be fine. But I'll need your credit card details first, so that I can pay for all the services you have agreed to pay for. (Edit) - this post looks a bit odd now, it was made in response to a handful of posts from someone who was refusing to read the previous conversation, and suggested transferring their systems…

You'll need to use the REST API to read the status of the issues you are displaying from Jira and put that data on your page.

No, there's no separate call to check credentials. Just try logging in with them.

This doc is talking about "simplified workflows" - these have to be enabled by a Jira admin before a project admin gets to edit them. Your admin needs to go to the board that you want to simplify for and click the button to simplity. This creates a workflow called something like "simplified workflow for board X" and…

Go to Admin -> System information, and read the Jira version, the versions of all the installed apps, and the "modified files" section. Patches to Jira are mostly done by upgrading to a newer version (and apps are all done by new versions), but sometimes, a patch is done by replacing or modifying one of the installation…

The whole point of "simplified workflow" is that a project/board admin can edit the workflow by adding and removing columns!

What do the logs say the problem is?

Yep, the standards are not complex: * A story is something your people ask for, and your developers work to deliver (within a sprint if you're working in a Scrum way) * An Epic is an over-arching thing that contains many issues, across many projects, and represents a longer-term goal. * A sub-task is a fragment of a story…

You only need one connector. I'd hang on to the one you don't want in the config though - comment it out, don't delete, you might want to fall back on it or have it around for reference when upgrading.

The Community have little say in what goes into the Jira developer's backlogs. You'll need to raise this with Atlassian as an improvement request, to get it into the queue with the other public requests in https://jira.atlassian.com/issues/?filter=98688 Make sure you detail how you would like to make things more visually…

Welcome to the Atlassian Community! Yes, but it is a manual process. You will need to open and amend every active issue type scheme, and then go into each team-managed project and configure them individually.

What are your directory settings for the user directory in Jira? Can you check the logs to see if there are synchronisation errors? (Quick trick here is to start "tailing" the jira application log and click "test" and "sync now" in the user directory screen). Is there a difference between a user that does sync and one that…

It sounds like https://www.atlassian.com/software/jira/service-management would be a place to start with Atlassian.

I think the error message is pretty clear with the 530 error.