Comments
-
Hmm. I'm using graphviz macros inside other macros, although the container macros are part of the core of Confluence. I think, more importantly, they're macros that render Confluence language internally, so they know where to go when they try to render another macro. I suspect your macro does not render Confluence data?…
-
Not really. You can use inline edit to change a field. There are no hooks for doing extra things that would annoy the user (popups and other things that interrupt a humans flow of activity are bad) Best option - remove the field from the edit screen so that they have to click a workflow transition to change the field. Then…
-
Thanks for clearing up my confusion! I don't think there's any way to do this on Cloud. If it were server, you might be able to play some javascript tricks (not recommended, ever) or use something like Behaviours in the ScriptRunner add-on to do it. But those aren't options for Cloud.
-
There are two different things in your question - making a field mandatory, or calculating something. I'm not sure which one to answer?
-
You have a field of a type provided by the "JIRA Misc fields" add-on, and it is configured incorrectly. I'd guess you've renamed or deleted a field it is configured to look at. Follow the link the error message is suggesting you look at and correct the configuration in there, I think it needs to be repointed to an existing…
-
Again, get the list of groups, then subtract the list of groups in use from it. You also need to think through what you mean by "groups used". If you read the permission scheme table, you can extract lines where you've got "allow permission to group X", but that doesn't cover the use of groups via role. Or group-picker…
-
Again, there is no way to do this because you can not search for a negative value. You need to * get the full list of all groups * search for all groups that are used * Subtract the used groups from the full list Some extra points here * You can easily modify Tiago's SQL to return groups in use instead of projects * Groups…
-
With difficulty, because you're looking for negative data. What you probably need to do is build a list of what groups are used and then subtract it from the list of all groups. You'll need to look through all the project roles, all the permission schemes, all the notification schemes, all the security schemes, any group…
-
A lot of places link the project to a Confluence space and then do the documentation there instead.
-
There aren't any. What you want is to check that the user matches a group. I don't know if there are validators available on Cloud that can do that.
-
Yes, that's the point of the answer. Off the shelf, you can't configure this - if a user can create, they can create. But you can set up a workflow that fails a validator and hence stops someone creating a certain type.
-
Similar discussion was had yesterday - see https://answers.atlassian.com/questions/45948115
-
You'll need to ask Atlassian about that, although I doubt they'll certify anything. Try https://support.atlassian.com
-
Apologies for the necro-post, but if people are still interested (and still happy to wait), see https://jira.atlassian.com/browse/GHS-9455 I'd still avoid renaming epics to something else, but a change of description, inline translation and changing workflows are all ok now.
-
It now sounds like you're hitting the wrong url. What urls are you actually hitting?
-
The message explains what is happening - it will revert when they've finished.
-
That doesn't seem to be related to your original question really. Check your log to see if there are import errors.
-
I suspect that you have no data for the fields that are not appearing. JIRA only shows fields which have data in them when you view an issue. Try editing the issue and putting some data in, then see if the fields appear on issue view.
-
I'd start with issuetype = story and "Story points" is empty
-
The way to do it is to modify the code to add the fields. But you can't do that on Cloud (yet)
-
No, you can't modify the code on Cloud.
-
You don't. You create a new board of the type you want, and delete the old one if you don't need it any more.
-
JIRA is not an email client, it's an issue tracker. But it can process incoming email (as well as send out the notifications when things happen inside it). Have a look at https://confluence.atlassian.com/jiracloud/creating-issues-and-comments-from-email-735941056.html
-
Edit the notification scheme to include them. Use the dynamic options - reporter, assignee, watchers etc. I don't know if OnDemand includes the "Jira Toolkit", which provides a "Participants" field, but that can be very useful too.
-
https://confluence.atlassian.com/display/JIRA040/How+to+search+in+a+plugin Looks old, but the code is still mostly valid, and the approach is the same for 5 and 6 Ah, crossed posting, sorry!
-
In the UI, edit the query in the advanced edit. If you mean in code, create a new query and save it over the top of the old one.
-
I think it's more up to the project lead to prioritise, especially bugs. One user screaming that their text is green instead of blue might well be a Major priority for them, but most teams would rate "200 users can't enter data properly" as a higher priority! One thing I've seen in a lot of places - an "unprioritised" by…
-
I think it's mostly based on the way the English language works to native speakers - major, minor, trivial, blocker etc, they all imply a sense of relative importance or urgency. "Normal" does not really carry any relative importance like the other words in use there, you won't find English speakers using it in any scale…
-
We need more information - your actual Jira version might help (6 isn't scheduled yet, and 5 certainly isn't out) That error usually means the server can't talk to itself for some reason - the gadgets sort of run outside Jira and request information from it, and that link is failing. You'll need to read the log files to…
-
Essentially, there's something wrong with the network connection from the Mac to the network.