when trying to use
/setblock x y z <block> <data> replace <NBT> at a position, were a block with the same id and data, but different NBT-Data exists, the command doesn't recognize NBT-Data change as a block change and the new block is not placed.
Related issues
Comments

I can confirm this. This is extremely annoying. I think it's unrelated to MC-30870, since it occurs when detecting at the correct location, but I'm not exactly an expert.
Essentially, this means that all changes to the NBT data of blocks done with /setblock must first change the block to something else entirely. Most noticeable in signs and command blocks. This makes designing redstone that uses the new features much more difficult than it has to be.
Until this is fixed, I've found that summoning FallingSand replaces the NBT data just fine, so I'll be using that.
Seems to be connected to MC-32289, if not a duplicate.

It's the other way round, this ticket was first.
I can confirm that this still occurs in 13w47c.
Confirmed in 1.7.4. Still annoyed this hasn't been fixed >.<
Caused by MC-30870 ?