Nic Brough -Adaptavist- Expert

On Cloud, it is <yoursite>.atlassian.net/jira

Project create (even in the more recent team/company-managed projects that replaced "next-gen" years ago) does not fire any events the email systems could pick up, so I'm sorry, but no. You can't do this. You will need an app to detect the project create and send out mail.

Welcome to the Atlassian Community! The updated date records the last change to an issue, but only the current issue. It includes edits, transition, comments etc

Hmm. The overall effect of this feels like a very broken "requirement". A field on an issue is not the right place to be trying to report on the number of issues in a project, and I have to question of what possible use that information actually is? Anyone who really needs to know it (and I can't imagine it's anyone…

No, your plan is supposed to be showing you the, well, plan. That's what it is doing now. If you want to "flatten" your plan, you need to flatten the data underlying it.

You have not told us what they think the threat is, so there's no way to know what to confirm or not. They're probably wrong, but without knowing what they're telling you, there's nothing you can do.

That suggests that the field, while it is in the card layout, has not been added to the Create or Edit screens for the issues of that type in the current project.

Welcome to the Atlassian Community! That should still work, but could you have a close look at the list of custom fields and check that you only have one Story Points field? Also, maybe try "Story Points" = 0

Ok, that's good to see. My original question was trying to tease out how you are expecting to get the data for the incident number into Jira, but it looks like you're not yet sure yet. The next thing to do is to either * Create a new issue - does it ask you to enter the field then? * Edit an existing one - does it prompt…

Welcome to the Atlassian Community! You can't just add a field and expect it to be filled arbitrarily from (presumably) another system. How are you adding the incident number to your issues?

Welcome to the Atlassian Community! It is not wrong. You have changed data in a way that means you are now reporting on things you were ignoring before. 

For JQL, go to Issues -> Search and click "advanced" All you need for watching is something like watchers = currentUser()

The only useful way to do this is to take a full backup of the system, in a format in which you can restore it to another (temporary or development) Jira system. Or, you will need to write something to scrape and export every issue into a format you want to keep. I'm not aware of any apps that can do the latter.

Ah, beat me to it! Glad you found it faster than I could respond! For anyone else landing here, the default value for fields is set in the "context" for the field, not the "edit" shown above.

There is not a lot more we can tell you, other than you will need to code your application to understand the markup it is fetching from Jira.

Yes, you can do this, but not exactly in the way you're assuming. Time-tracking is not a simple field, it's an accumulation of several informational items on issues, and is actually made up of several things, some of which work very much like fields. The main ones you'll want to consider to be a part of time-tracking are…

If your entire browser is "abruptly closing", then it has to be the browser. Jira can't tell your client machine to close applications.

What is the default text for the field?

In a Service Management environment, assigning to a group is not a good practice. The better way to do it is set up Queues and make each "group" responsible for dealing with a queue.

Welcome to the Atlassian Community! This is what it says it is - you don't have access to that system. You will need to talk to the administrators of it. Who asked you to use it? They're a good starting point for finding out who you need to talk to.

You will need to code your asp.net application so that it can parse and render the markup into the format you want (or ignore it and strip the markup out)

Yes, convert all your sub-tasks to base-issue level issues, as you don't want to see them as fragments of their parent issues

>Would all issues, workflows, fields, etc be the same? Almost. JSM will add some fields and functions to your project, primarily the ability to put a "Request" in front of an Issue, but it won't change the existing fields or workflows. It may warn you that the existing workflows won't work well for JSM projects, and you…

Yes, only administrators can create and maintain company-managed projects. You don't want most of your users to be able to do that, I can guarantee you that they will make a complete mess, and probably end up destroying data that you really can't afford to lose.

Welcome to the Atlassian Community! I think the problem here is not that Jira is returning stuff in an unreadable format, it's that your asp.net code does not know how to read it. The examples you've given here look like rendered text - it contains control characters that are telling you how the text is formatted (bold,…

Generally, a node should be sized the same as a single server. As you already have a working server, that's an excellent starting point - spec your nodes to be broadly the same power as your existing server. How many nodes is a question we can't help you with. A single node does not get you all the benefits of a DC…

Yep, the point of the board and the sprint is that it represents the work of a single (multi-functional) team, not a set of siloes. When a team gets into a position where they've only got a couple of stories left that they committed to, they know that the people working on them are going to get them done and others in the…

Welcome to the Atlassian Community! "Not opening" does not give us much to work with. Could you explain what you actually get? An error message? A blank page in the browser? Something else?

It appears because Atlassian want to offer you the option to sign up for one of their mailing lists. Ignore it for now and it'll vanish after the first couple of times you log in.

Which then begs the question of why you've got six pages of text in an issue-tracker when it should be in a documentation system, or why that should work differently to every other field in the system. I can select text without fear o a 6 page scroll in Jira long-text fields without problems, I generally choose not to,…