Comments
-
Boards do not contain issues, they are a view of a selection of issues. You can have many boards looking at the same issues. Your delete of an issue removes it from JIRA, so any boards that used to include it will have nothing to show.
-
No. The whole point of the "can be assigned an issue" permission is that you limit/allow the right people. If you want to assign to someone not on the list, you need to get them added to it (which depends on your permission scheme for the project)
-
Sorry, too many mechanical engineers in the family - the cog is the circular bumpy icon near the top right that you click for admin functions. Based on those things you find in steam engines and watches etc. I should be more clear about that!
-
I think you've misunderstood me, sorry.You do not change the template. If you were to create the project "manually", you would have to make a whole string of decisions about what "schemes" to use in the project (notifications, permissions, field config, workflow, issue types and so-on). A template simply answers those for…
-
You need admin rights to delete a project, but if you do it, you destroy it completely. However, the "project type" you want to change is actually not stored data, it is a template. To convert a project from Scrum to Kanban or vice-cersa, all you need to do is change the "schemes" that configure the project to the ones…
-
You'll need to write something to do this. I'd suggest a listener that looks for "work logged" events, scans them to see if they should be duplicated to the other Jira and posts them over via REST if they're needed.
-
Good, so it's a general error and not a field-specific one. Next question is if your REST can see system fields? Like *summary* for example?
-
Can your REST see any other custom fields?
-
mmm. Check the field exists in the project/issue-type, and that the user that you are logging in as can see it too.
-
Actually, I very much doubt that field exists. Customfield tags are usually 5 digits long and start at 10000. Have another look in your installation, I think you'll find it's customfield_10004 or customfield_10400 !
-
What do you mean by "item in a retrospective"? Generally, a retrospective is a talk about how the last sprint went. There's no need to "vote" on things you discuss, you're just talking about what was delivered, what was not and so-on. The items are more likely to be "work items", which you handle in an issue tracker. If…
-
Ah, ok. I can't think of any proven way to do that, but I suspect you could look into * Adding javascript to the announcement banner that says "if user in group X, then show this bit" * Using the text gadget on the default dashboard to do the same * (Ugly, but needs no code) Add a project gadget, showing the brief view of…
-
What do you mean by "update"?
-
The xml looks right to me, I think you need to expand on the error message - "invalid field type" doesn't tell us much. What does the full error say?
-
Start with http://confluence.atlassian.com/pages/viewpage.action?pageId=236588798 Note - there is a page for 4.4, but the "include" it uses has been broken, so it's not working. It's almost identical though - the basic idea is to add a searcher to your atlassian-plugin.xml that says "use this searcher". If you want to use…
-
1. Yes. Try a search for, um, Balsamiq 2. Yes 3. Yes 4. Read the documentation, read the web, and ask here (but ask specific questions here - generalisations won't get you far, because you should be able to get better answers more suited to your needs by reading for yourself first)
-
Same here, although I did it with a workflow post-function as part of the requirement was to track the users who added/removed users from certain groups.
-
Possibly. Licences are by seat, Atlassian don't really care how you allocated them. If you want to drop a "client", assuming that means "our client has 5 accounts in our system", then just disable the 5 users and enable the users for the new client. If you're talking more about having a JIRA/Confluence set dedicated to a…
-
Click Jira admin (cog near top right) then issues, then look to the bottom of the options on the left hand panel.
-
Rambanam has given you the correct answers, although I'd suggest a post-function is better as you only want to set one value. However, you must remember that setting the resolution will make Jira believe that your issue is "resolved" and hence crossed out in the UI, ignored in many reports because it's finished with, and…
-
Is their email correct in Jira? Look at the project, and find the notification scheme for it. Go into that and check who is supposed to get notifications for which events. Does the user actually match those settings? As an administrator, go to the email server settings in Jira and try sending them a test email. Does that…
-
It's a global permission, not in the permission scheme
-
Use @username in the comment. You must have the global permission "browse users" in order for it to work though
-
Ah, ok. The thing to try here is an import such as: TypeParentEpic LinkSummaryEffectEpic My EpicYou get an epicTask Do somethingAn independent taskStory My EpicA storyStory, as part of an epicsubtaskStory1 do stuff for story1Subtask under StorysubtaskStory1 do more stuff for story1Subtask under story
-
JIRA Core only does task/sub-task. Epics are just seen at the same level as tasks in there. JIRA Software allows Epics to effectively become groups of tasks/stories/whatevers
-
Natively, JIRA is not a time sheeting system, the work logs are for recording time spent on issues, not time logged by person/month/project/etc. So it's reporting on that is not so strong. However, if you type "timesheet" into the marketplace, you'll find add-ons ranging from basic timesheeting reports through to full-on…
-
You need to amend the templates to include the fields. See https://confluence.atlassian.com/jira/customizing-email-content-185729653.html
-
Generally, ask other users or look for the "contact administrators" link at the bottom of the page or on your login page. If you can't identify them at all, then your only choice might be a support call with OnDemand support to extract who they are from the data in your JIRA.
-
Not really. Your other option is to write a mail handler that only does the bits you need (instead of the huge range of functions that JEMH can provide)
-
Yes, I'm afraid you've run into the inherited default group problem. JIRA ships with jira-users as the group that defines "can log in". That's fine on its own, but they then go on to use this group by default as "can use project". Again, that's fine, until the first time you realise you need a less visible project. At this…