Comments
-
Remove the user's rights to comment on the issue.
-
Code. You'd need to adjust the template file that is drawing the field. I think it's called radiobutton.vm and it's buried deep within the core of the application. If you do change it, you'll need to remember to reapply the change on every upgrade.
-
Same answer - it's not going to happen.
-
No. Sorry. Jira issue keys are generated sequentially within the project. You can't change it without a massive rewrite of core code. A number of sites I know of have assorted work-arounds. One I coded was a simple derived field that displays the parent and child numbers together (it's aimed mainly at sort on the…
-
Ah, sorry, I usually take a copy of it, which you can then edit. But it's also on https://confluence.atlassian.com/jira/workflow-properties-189949.html
-
You can edit a field in two ways basically. If you have it on the "edit" screen, then it's editable when editing the issue or by clicking in the view screen, and in places that support edit functions. If you remove it from there, it's effectively read-only (barring place 2) If you put a field on a transition screen, then…
-
No. You can use workflow properties to block all edits when in a status, but not field edits. The way to handle what you're asking for is to move edit into the workflow, as mentioned above.
-
Hang on, there's a whole lot of totally unneccesary code being thrown around here. Peter's original answer is correct, as is Henning's follow up. Put the field on the CREATE and VIEW screens. Do not put it on the EDIT screen. The user can then add data to the field when it is created. They will not be able to change it…
-
This is just duplicating what JIRA automatically writes into the issue history, you don't need it. You can't do it on cloud either, it requires some scripting or code that you can't do on Cloud.
-
Depends on what you can do with your VSM system. Sending an email to JIRA is pretty basic. You can't parse fields, do defaults or complex updates (just comments really) with the standard handlers, you'll probably quickly find that you want something more clever and hence need an addon to provide a more flexible/powerful…
-
Um. The Behaviours addon is free, like script runner, so I'm a bit confused by that statement. Also, in later versions, Jamie has effectively merged them together, so if you're on JIRA 6.3 or above (and on the latest version of script runner for your version of JIRA), you have Behaviours as part of the Script runner. That…
-
Technically, yes you do. Your Agent licences include a Core licence. If you want non-agents to use JIRA, they will need Core licences (or Software licences, which also include Core) If, for example, you bought 3 agents, 25 developers and 10 Core licences, you could have a maximum of 3 Agents, 25 Software users, and…
-
There's a good introduction in the form of a tutorial on https://documentation.riada.se/display/IN/Insight+-+Overview - do not skim the "concepts" section lightly though - I did, and I ended up going back to it. (Ok, kept it open in a new tab and jumped back and forth)
-
JIRA won't do that off-the-shelf, as it's an issue tracker, not an asset management system. That said, a lot of people do use it for asset management, including "joiner / mover / leaver" type stuff. The usual approach to that is to set up an issue that represents each user. In this case, you'd need to be doing all your…
-
Looks like you've run into a bug. It's logged at https://jamieechlin.atlassian.net/browse/GRV-368but there's no answer for it yet. I'd check the obvious - what version of Java are you running? Can you try a slightly lower version of the plugin and see if it happens there as well?
-
For a standard custom field, simply remove it from the "edit" screen. I don't want to talk about other variations on this without a bit more information on what you're trying to achieve (telling you to do it in Behaviours when you actually would benefit from doing it in workflow would be a bit of a waste, etc)
-
You can fetch the attachment over REST, as Boris has said. And it's no good saying "CORS problem exists" without telling us what you think CORS means or what the problem is.
-
I guess you mean "Project", not "protect"? If so, then you just log in as an admin, go to the project list and click "create"
-
Have a look at https://confluence.atlassian.com/display/JIRA/Jelly+Escalation That takes a filter, runs it, and then attempts to do something to each issue returned. The examples given are "comment" and "move through workflow" - you need the second (workflow move = status change)
-
I think you need an "Auto transition listener". Try the one in the JIRA Toolkit addon - it was written for the cases where "user comments on closed issue instead of reopening it", but it more flexible than that.
-
That sounds like there is damaged data in your database. Could you read the log file to see what that has to say? It should repeat the "Unable to read BLOB data" etc, so you could open it in a text editor, search for that, and read the log for errors immediately above and below it (java errors tend to be long, but indented…
-
It is. Your version of Behaviours is not valid or supported on that version of JIRA. You need to remove it from your installation and install a working version. As it's now part of "Script Runner", you'll need to install that instead.
-
Yes - as an admin, go to issues -> custom fields, and click "add". Answer the initial questions about name, starting content (options) and screens, save it and you'll have the field on your issues. To add/update/de-activate/delete options later go back to admin -> custom fields, and change the config of the field
-
Yes, you can only "manage labels" via issues. Labels are not intended to be "managed" centrally, they're for users. If you want to use managed lists of words/phrases, then use a multi-select field instead.
-
You've set the permissions incorrectly, or deleted or moved the cache directory, so Tomcat can't use the directory. The usual culprit is that you've started the system as the wrong user, which writes to files in its own name, so that when you start it with another user, they can't read/write/delete the files. Check who is…
-
Create project is under the projects menu. The create button is for issues only.To create new projects, you do need admin access - have a look at the admin cog in the top right corner - that may have three values -- it's not there - you have no admin rights at all- it just talks about projects - you are a project admin for…
-
What do you mane "keeps defaulting to the first one?". You should be able to click "create project", select a template to create it from, answer some questions, and it'll land on the newly created project summary screen. Where is it deviating from that route? Or where is it going wrong in there? (I've a sneaking feeling…
-
1) Radu has that one answered 2) Yes 3) Two years is too long to be counted as "renewal", and it's probably not worth it. You will find it cheaper to buy a new licence for a year (this doesn't affect your data, a licence just says "I'm valid until xxx, so you can use any JIRA data, old or new")
-
Start with https://confluence.atlassian.com/jirakb/troubleshooting-jira-startup-failed-error-394464512.html
-
Ta, I'll close this one as "mostly useless" then ;-)