Nic Brough -Adaptavist- Expert

This is exactly what it says it is. Do not run Bitbucket as root, it is insecure and does not work. Try running it as the bitbucket user.

Welcome to the community! This usually means what it says - there's a problem reading and writing the disk for some reason. Sometimes, this is down to unsuitable storage, or you (as it says) have configured it with too small a disk allowance, but the usual culprit is that the account running Bitbucket does not have the…

Welcome to the Community! I am sorry, I am a little confused here. Jira is a web service, so the "native" app really is "using it in a browser" I suspect that you've got one of the Jira client apps on your device, so what you probably want to do is set up something on there that will spot when you try to visit a Jira url…

I do not think that the OR is the problem here, it's the order in which the clauses are read - I think you're expecting the clauses to be joined differently to the way they actually are. When you don't enforce precedence with parenthesis, Jira, will read left to right. I like simplifying these down to make them more easily…

Welcome to the Community! You'll need to do some scripting or coding to perform the functions that your "integration" will want to do. Start with a look through https://developer.atlassian.com/cloud/jira/service-desk/rest/intro/

You can put an issue into two sprints, but remember that this will break it for the team that does not deliver it completely. Generally, you shouldn't do this - there's two separate pieces of work to do here, with two different teams, so there should really be two stories.

>Are you both stating that I need to create a field configuration and add these fields to the subtasks? No. Field configurations do not add fields to issues. They are a handful of flags or settings for the fields. Your project is using one field configuration, and you've said "field X is mandatory" in it. If you create a…

What do you mean by "component option"?

I suspect the way forward is to do what the document says. Go to Admin -> Issues -> Custom fields, find the Story Points field and change its context, so that it does not apply to any sub-task types.

Oh, as an aside, we should be careful - if the marketing people at Adaptavist see this thread, they might start "borrowing" logos again. (Says he who is wearing an Atari-test-management shirt, carefully selected from between the ScriptRunner-bladerunner and Scriptrunner-coke shirts, next to the Harley-davidson-summit shirt)

See the answered thread above.

Welcome to the Community! I'm pretty sure the field you are talking about is not a field, it's a display, generated on-the-fly when a human lands on a page where it needs to be displayed.

"issuetype in (Story, Task)" would do it.

Yes, you could create a local batch file that can poke an issue (with attachments) into Jira over the REST API. You'll need something that can hit the REST endpoint with your data - I tend to use curl in scripts.

Do you mean you want to put things in the field on issues, or are you talking about the options on a select list? What exactly is the field type?

Ok, and what type of field is this custom field?

There is no way to do this, Jira is built to show you everything on the issue.

Ok, that makes sense. The report doesn't show anything until it's got enough data to be actually useful - you'll need to complete another couple of sprints before it will do anything.

I don't really have too strong an affiliation with any particular brand. Adaptavist and Atlassian obviously leap to mind, and then a couple of places I enjoyed working and was there a while - BP (BP Amoco at the time, I was there when before rebranded to bp and stole the flora logo they use now, and most of my swag from…

Yes, you can model any process flow you want in Jira

Yes, you can have different conditions on different types of sub-task because you can set up different workflows by issue type. If you've got a scripting tool added to your Jira, you could write more clever conditions that could look at other data. The answer I gave before is using built-in functions.

No, the assignee is a single person, the one who is currently responsible for getting an issue done. Jira does not allow multiple assignees because it does not work in real life, and you should never do it. Nothing wrong with having other people named as "who to talk to if <assignee> isn't around" or "other interested…

It's limited by the size of the field it gets stored in in your database. Last time I looked, I found a doc on Postgres that said a text field was limited to 1Gb, so that's the most you can put in a Description field if you're on Postgres. I think a more useful answer is probably just "a lot more than you would ever need…

The project type has no effect on searches or filter results. Can you show us the saved filter you are using? (Not the results, and feel free to replace project names to obscure them) Then can you tell us about your status mappings into columns on the board?

Sorry, but I'm offered Issue Type in the field mapping, so I don't know what you're missing. Could you already have mapped it to another field?

Why are you trying to connect to that system?

You can simply search for "Link to Content" is not empty

The only way to stop an issue being moved into a project is to take away the person's right to create issues in the project.

Yes, you will need to change the board filters. You'll need to get them to be exclusive on the basis of what you want the sprints to cover, for example if board 1 says "project = x" and board 2 is "project = y", then they will never include the same issues, so their sprints will not appear on the other board.

That is a good point. We have a cruddy timesheet system that demands a comment on every entry. Our developers quickly wrote a script to automate "working on this" to go in automatically, and 99% of the comments are just . "working on this" or "did stuff" type copy and paste things.