C.Faysal {CFcon} Community Champion

ah ok i thought you only need to differentiate them on the board. sorry maybe some manipulations can be made by adding some step properties in the workflow section but i am not sure

so it won't help if you setup two cardcolors with different queries to match? locally i've added RED with "status = closed" Orange with "status = resolved" wich correctly colors up the cards matching to the queries

ok tell me exactly what goal you want to reach. maybe missunderstood your request

you can change the cards color for any resolution (using jql query) or status in Board Configuration. see attached screen for example

my opinion is it refers to the date you started logging work on the issue. i tested on an issue that was created on monday (feb 18th) when i click "log work" from more actions the "Date Started" field value is set to today

i agree with renjith. just like we discussed here https://answers.atlassian.com/questions/119803/how-to-disable-edit-operation-button-and-live-editing-for-users permissions would be the smarter way. but if you insist editing velocity files be informed that you will need to copy them back after any upgrade you make. also…

you can try purging the work directory to force a rebuild. plugins caches as well work dir is in install path and plugins cache in jira home/.bundled & .osgi-plugins

what jira version are you on? what action did you do to make jira recommend a reindex?

i deleted my answer...didn't knew that onDemand differs in that case :)

hi. you will need to create a new group i.e. jira-system-administrators. put your user in that group edit global permissions and choose this group to have "Jira System Administrator" Permission

i just added a "Value Field" condition to a transition where i chose "issue type" and set = to an existing one. which makes the transition only available if the issue type is (in my example) a story. any other issue type won't show this transition if you need some of your transitions for more than one issue type simply add…

this will be not that easy to achieve. keep in mind that some IDs will be the same but the values are differing... i.e. custom_fields, workflows, permissionschemes etc... i suggest to setup a test instance and import projects. i expect a failure using full backup & restore. on the test system you should.. 1. full restore…

you're welcome

yes of course you can add a condition to the transition so that only users of a specific group can transist the issue backwards. please see this KB article https://confluence.atlassian.com/display/JIRA/Configuring+Workflow#ConfiguringWorkflow-conditions regards

only content restore...i did yesterday. i restored content from other version into latest eap release...just for testing if you need help just let me know so we could connect somehow..maybe skype.

hmm Caused by: org.apache.poi.openxml4j.exceptions.InvalidFormatException: Absolute URI forbidden: file:///C:/Documents%20and%20Settings/miika/My%20Documents/Tikkuukot.vsd/Drawing/~Physical%20DB%20Setup/User.55 i wonder where this is comming from. could you backup your DB, confluence_HOME and confluence_INSTALL Directory…

all content lost is something i don't believe. i'd like to see the steps you took while performing the upgrade. let me guess... you downloaded the right binary for your system. (32/64 Bit chosen correctly) after adding the x flag to it you ran ./atlassian-confluence-XX.bin was this one offered to you? "press 3 to upgrade…

yep. https://confluence.atlassian.com/display/JIRA/Associating+a+Screen+with+an+Issue+Operation

What about opening a new topic?Feel free to accept the answer if it was helpful and open up a new request to reach more possible helpers by showing the related info in the questions summary ;)

What about global permissions. Are the new users in the correct group that is permitted?

Isn't there a license section in administration too?

What about filtering "jira-users"?

Administration/Users you will see a line such like Displaying users 1 to 20 of <someNumber>

users that are in the group "jira-users" have the possibilty to login to jira. for confluence it should be "confluence-users" those count against your license. so just add your 2-5 users to this group

try <jira_host>/rest/api/2/issue/<ISSUE-KEY>?expand=changelog

raimonds...oops :) you're right

check -> http://youtu.be/klVGjIn5JZ8

oh a different one? hmm no...the same :D

did you checked https://marketplace.atlassian.com/plugins/EAZYBI

Hi. do you have the init script installed? if i am not totally wrong then the user jira is set inside there... so this is the reason you can start jira using "/etc/init.d/jira start" as root user and the process owner will be user "jira" as renjith already stated it is not recommended to run any service as root user. stick…