Comments
-
Yep, create numeric custom fields for the various estimates, then I'd use Scriptrunner to add them up for display, search and reporting.
-
The url you've given to a project is a url for linking the project to another system. It's just plain text data you'll need to edit if you've moved the target.
-
Set up different issue types with the fields you need to capture, and leave off fields you don't need for each type. That obviates the need for templates, as you're only asking for stuff you need.
-
Indeed it does not, that's why I try to explain what is happening when people bicker about it
-
Licences are by server (until you get up into the numbers where you're looking at site licences). You can buy a 10 user licence, but it will have to be used to run a separate 10 user server. You can't add it to an existing server to add a few more users.
-
You will need to write an add-on to provide this if you want to do it properly. Otherwise, you could use a text field and then wrap some "Behaviours" around it to validate the entry is good. But Behaviours can't stop people getting it wrong in several places, so you'd also need a listener to catch changes to the field,…
-
See the other accepted answer above.
-
Go to the screen with the column definitions. Drag the status into the right columns for them.
-
It depends on the contracts you have with them. IR35 does not preclude the logging of time, but any form of time logging can be counted as evidence that your contractors are actually employees. If you need them to log time, you might as well do it in Jira, as any logging system is going to run into the same problem.
-
Quite probably just Confluence itself - it has revision management built in. Not sure what you mean by "insert our norms" though.
-
Throw away your "status" and "status to" columns as they're nonsense. Treat the "sub-status to" column as status, as this is what your process actually is.
-
The JQL query you need is project = abc and type=epic and status=done Queries usually run in the issue navigator, to which you can choose to add fields. The fields Epic and Summary can be added by default, but the other three you have need to be calculated by code, as Jira does not have them natively. Do you have one of…
-
Sub-status does not make sense - the status is there to tell you where an issue is in your process. Imagine status as something that is completely clear as to where something is - "It's in progress", "We're working on it", "We're done". Sub-status is bad, because you could say "we're working on it, but not, at the same…
-
I can't add to Alexey's answer here - that's exactly the page I'd refer to as well.
-
Were these "closed" issues in the last column of the board when you ended the sprint? Is the "done" status in the last column on the board?
-
>What I am trying to develop is an scripted field that runs when a ticket is cloned. Scripted fields show a calculated value, they don't hold data. They don't "run" during events, the easiest way to think of them is that they calculate the value shown when an issue is indexed. That said, I can't see that your code is…
-
You get a stack overflow because your code calls out to get the field which runs your code that calls out to get the field which runs your code that calls out to get the field... That recursion stops when the process runs out of working space in which to repeat itself. What you're doing sounds like nonsense to me - a…
-
That's only part of what you did, could you continue with the rest of the steps you took to get the error?
-
Ok, so exactly as we said earlier - the issue is in a status you have not got mapped to a column on the board. You need to map the status "in development" into the to-do or in-progress columns on your board.
-
You can install it, but you can't run Bitbucket on it (safely) - it's not supported and may well fall over without warning. This may change in the future check the version of Bitbucket you have against https://confluence.atlassian.com/bitbucketserver/supported-platforms-776640981.html
-
Only the basics, the JIRA API does most of the work for you, you just need to learn how to talk to it.
-
Find something that you want to do with the API first, and then code to that. It's a lot easier to learn something by working your way through the process of building something useful! The internal API is Java based so if you mean that one, start with Java, but the external one returns standard JSON, so you can pick any…
-
Choosing another server just because Bitbucket doesn't do one obscure thing that most people haven't even heard of, and even more don't care about, seems a little odd to me. I'd think about writing an App to do it, if it's that important to you.
-
If they're using the customer portal, then they've created the issue there and don't need a notification because they've just created it. If they're creating it by email, then they're not looking at the portal and probably need an email back to confirm it. I don't think your suggestion of telling someone that they've just…
-
But there's no harm in adding Reviewer and Tester as custom fields. I'd suggest using the user-picker type for them.
-
That usually means that the service is not running. Can you check that it is?
-
What do you mean by "list view"?
-
Ok. So rather than dancing around with screenshots showing us parts of your config that then change, we need to nail down one fixed case. * Pick an issue that should appear on a board. * Pick the board it should appear on. * Log in as a user who can see both. * Give us the board filter * Give us the column definition for…
-
Could you give us the steps you took to get to this error message?
-
This seems to be about the legacy system "Remedy" rather than any Atlassian system. Could you explain, and go into a bit more detail about your workflow and process?