Nic Brough -Adaptavist- Expert

You don't need to, it is built into Jira. But if you do want to build it from scratch, download the source code for Jira and compile it. I think there is a bit of a problem in our understanding of each other here. Could you explain what you are trying to achieve here? Not the implementation (technologies in use, code etc),…

Khoros (the software behind Community) has a bug where it pads urls with invisible junk when they are pasted into it. I've re-done the link, please try it again.

Your specific users will need to be added as Confluence users so that you can give them the right to use a space or page.

No This is because you really really do not want to assign something to a group. If you do that, you can be absolutely sure that issues will fail to be addressed because members of that group think someone else will be dealing with it, and you will have people outside that group yelling "well which one of you is actually…

You have defeated me on templates, I have not used them, sorry. I have used the "Manage API" to create an incident from a shell script, but it does not use anything clever like templates. (It's not even as clever as my "post text into Slack" script and that's pretty much a raw https call with a hard-coded token, which I…

Sorry, I missed the "full statuspage incident" part, I was too focussed on integration with NewRelic. I don't believe you can do that with NewRelic off-the-shelf. The reason I say that is the table 3/4 of the way down https://support.atlassian.com/statuspage/docs/know-when-to-automate-your-status-page/ under "Automating…

I have used https://support.atlassian.com/statuspage/docs/add-a-new-relic-metric/ to get metrics into Statuspage. But I actually think you've answered your own question when you used the word "monitor" - I think https://support.atlassian.com/statuspage/docs/set-up-new-relic-alerts-parsing/ does what you want!

The problem you're having seems to be a result of not using it as intended, not a problem in the software. I would question why you are doing that and look to fix that instead of asking to reduce the functionality of the software.

I used the wrong phrase in the wrong place there. My point was that you can already get the behaviour being asked for. That people don't quite get that, or it's not obvious, those are not edge-cases. 

That's the project settings, you need to follow the rest of the clicks I mentioned to get to the issue type configuration.

This is down to your use of rbash for your shell - that restricts many of the functions that bash (and most other shells) do. One of the things rbash prohibits is the use of redirection of output, the > in your command. I think you'll need to run the command in a less restricted shell.

I'm not quite sure what you are trying to do here - you mention webhooks, but then give us a url that looks like you are trying to ask Jira to do something. Do you mean you are trying to configure a webhook in Jira to do something, or (which I think is more likely), you are trying to configure a webhook in another…

Ok, so if you have a look at the call as documented at https://docs.atlassian.com/jira-software/REST/7.3.1/ (look for the line "get issues for board" and click to expand it), you'll see an example response Near the end of the example, there is a block of json entitled "worklog"

Ah, if you don't have "where's my field", then you are in a Next-gen project. These do not use screens or field configs in the same way as Classic projects. Go to the project settings -> Issue types and select "user story". That's where you can add fields to an issue type for Next-gen

Continue to log effort as you do already. If you want to adjust the estimate to reflect that the task has grown, that's fine, just amend the remaining estimate upwards.

If you click on "create" and get the create issue dialogue, can you hit "configure fields" at the top right? Is your field enabled in there? You might find "where's my field" tells you more as well.

There is no way to cascade restrictions down like that in Confluence. (There was for a while, but it was removed rather quickly after all the screaming about how it messed up so many people's security) You will need to find an app that can apply your restriction when you need it cascaded. Obviously, I'll mention…

Just one of the real-world examples I've run into - some people want to do it that way. If you're waiting for someone else to release software for example, then why should their time be counted against the performance? Neither the agent nor the customer are counting.

It's not stored, it's generated on demand. You'll need to monitor it via REST

That depends on what your admins might be intending them to mean. Probably worth looking at them in the context of the workflow using them. My guess when I've seen them is that "waiting for support" is waiting for support to do something and move the issue along. Pending often means "pending something neither support nor…

I can't see a doc that says you can get to an issue via a board that way. rest/agile/<version>/board/<boardid> does have an issue function, but that returns all the issues on the board. The url you've given is not a valid call, but if you drop the issue number off the end of it, then you should get all issues on board with…

Scriptrunner is a good option (I would say that of course, I work for Adaptavist). There are other apps that can do validators of course. https://scriptrunner.adaptavist.com/latest/jira/tutorials/scripted-validators-tutorial.html is a starting point if you want to do it with a validator, but behaviours might be an option…

It depends on what you plan to store "documents" as. If your documents are translatable to Confluence pages, handled by and edited in Confluence, then the answer is yes, as that is what it is for. If your documents are lumps of data designed to be edited in other systems, then no, Confluence is probably a very poor choice.…

Yes, there is a way - revise all your permission schemes to include their access.

You'll need to ask the people who designed the workflows you are using. Some of these are distributed as part of the default workflows Jira provides (mostly intended as starting points) and they have names that have been designed to be self-explanatory. Your list has some that your admins have added, and they've also tried…

To check if a field configuration scheme is applied to a project, read the project configuration settings - the fields section will name all the schemes currently used. To rename a field, go to Admin -> Custom fields and edit it. It doesn't matter if it is mandatory or applied to certain issue types.

So how have you re-written Jira to use Solr instead of Lucene?

You will need to go through every permission scheme and make sure your READ_USERS group is included in the "Browse project" permission, and then check that the members do not get any other permissions because they are in other groups, or roles in the project.

By definition, users you have flagged as inactive do not count towards your licence limit.

Jira does not have a separate "can create project", you're either an admin (who can), or you are not. Most of us who have this requirement for non-admins to create projects use an app to do it - a web-fragment or workflow action backed by a create-project script, usually copying the settings from a template, or a…