Comments
-
No, you've missed the point - sometimes it's illegal to destroy the data. The content. Recording the deletion is useful for the prosecution. There very much are legitimate uses for "destroy my computer". In fact, exactly the same use case as you gave earlier. So coupled with your statement about the ease of doing it,…
-
No. Absolutely not. It should be very heavily protected. As I've already shown, in some cases it is downright illegal to destroy data, so you should always track it. As a general rule, it absolutely should be hard, to lower the chances of accidents. I don't understand how "yes, you have a case, but that is not a reason to…
-
I think the systems are in use for very different things - there's quite a lot of places where we have to completely disable the ablility to delete or amend anything in JIRA, because it's for tracking (the worst case I've seen is someone arrested and cautioned for deleting tracking data). You do have a valid use case, but…
-
An issue tracker that allows for the easy deletion of what you're tracking? It's actually more likely to go the other way and make sure no information is lost - there's loads of people asking for "edits/deletes of comments need to be recorded".
-
You can delete comments and they'll be destroyed, but not the issue history. You need code or database hacks to expunge them.
-
I should have said you've found a script which is pretty close already, it should actually still work (if you changed the XOR to OR and possibly made some updates to the calls, as the JIRA APIs have changed)But SR has functions that simplify the need for such code, so I thought you should try them first
-
Script Runner has moved on a bit - see https://scriptrunner.adaptavist.com/latest/jira/builtin-scripts.html#_simple_scripted_condition You should be able to do it on one line now - || cfValues[<span class="hljs-string">'MySelect2'</span>]<span class="hljs-string"> </span>cfValues[<span…
-
Use a scripted field from the "Script runner" plugin. You can't do this in native Jira, so you'll need a plugin no matter what - if you write a function to duplicate the data or just show it on-screen (a scripted or derived field - not actually stored in the database, but looks like a read-only field, can be searched and…
-
I'd start with the REST tutorials - https://developer.atlassian.com/jiradev/tutorials/jira-rest-api-tutorials
-
Repeating the question does not explain it. What is a "four time email notification"?
-
I'm not sure that's evolution, I suspect it's a dodgy translation program.
-
I'm sorry, what's a "4 time notification"?
-
The Classic boards (and their associated functions such as this gadget) were deprecated a long time ago, and are not available to Cloud, as they're unsupportable there.
-
Check the permission scheme for the rules that allow access. Then add the user to the right roles/groups
-
What exactly is the full text of the error message? Can you comment on other pages in the same space? Or other spaces?
-
Ah good, I wasn't sure it made much sense, as I'm not sure of the question, but if it does, great!
-
Sorry, your first paragraph makes no sense to me, which makes the second a bit hard to answer as well The trick with the workflow is simple - don't put the field on create or edit screens. Only put it on view and a transition screen. Then protect the transitions you want to change it on with conditions.
-
You could set it with a post-function on create-issue if you wanted to, yes. After creation, it'll appear on-screen for everyone, but not on edit screens for anyone. You then protect the edit of the field with conditions in the workflow.
-
No. This is pretty much the same as your earlier question about field security. You CAN do this by moving edit into the workflow, but that workaround doesn't apply to the create transition. I could explain more if it might be useful, but it would only help you if you are willing to accept that the field would not be…
-
Add a user who needs to be admin to the admin group. Then you can disable the internal admin account. (If you use LDAP and need to recover without it, you'll need to re-enable the user with SQL to get things going again, but it's not that much of a hassle.)
-
Look at the board filter to see why.
-
On the left, next to the avatar of the person who answered it. You MUST be the person who asked the question. The last time this came up, the questioner was logging in with a different account.
-
Do the boards include projects that the developer may not have the rights to see? Are you using issue security? Are the developers likely to be filtering in any way?
-
Unlikely to be a plugin, unless you've installed some really dubious stuff - I think you need to look closely at the emails to track back where they're coming from. What is the (non virus laden) content? Subject? Most important - what do the headers say? It could be just that someone has found the outgoing email address…
-
Look in the searchrequest and gadgetuserpreference for the direct reads of filters and dashboard gadget configs
-
The SQL would only be able to fetch the filter strings, and the whole of the board config, finding exactly where a custom field has been confiugred for use would involve knowing how to interpret all of that.
-
Ah, "swimlane by story" doesn't actually mean "by story", it means "by any parent issue". It doesn't care if you're using stories, bugs, issues, features, penguins. You get one row per *issue* and you can expand/collapse the display of subtasks under each issueFeature requests are made at…
-
>We came up with the concept of having a different board you can display only the sub-tasks of a specific issue Ah, that's bit I was groping for and not quite seeing! I'm going to blame mixing up the decaff with the real coffee this morning. Thanks for clearing it up! You're right, JIRA Agile does not support that in any…
-
I'm not entirely sure what the requirement is here - you've kind of outlined some stuff that doesn't seem to be right for you, but not really explained what you're actually aiming for. But * On the (parent) issue view, in plain JIRA (not Agile), it is possible to use the cog on the right of the sub-task list to transition…
-
If you are on Cloud, the cost is $10 a month. If you are on Server, running it yourself, then it's $10 for the year. I suspect you have mixed up the types of offering.