#1966 Confusing semating of dependencies between tickets
Closed: Fixed Opened by lslebodn.

It is possible to set dependencies between two tickets: either depends on or blocked.
In theory blocked might be a typo because JSONs imported with pgimport has attributes blocks and depends. And I tried that attribute depends is mapped to the field depends on.

I will describe steps which I done in staging instance https://stg.pagure.io/dependencies-test/i
1. Create a tracker ticket 1 which must be closed as last one. Title "Tracker bug" https://stg.pagure.io/dependencies-test/issue/1
2. Create 2nd ticket which should be implemented before ticket1. " Implement sub-feature1" Title https://stg.pagure.io/dependencies-test/issue/2
3. Jump back to ticket1 and set depends on. I added "#2" to the field.
4. Jumb back to ticket 2 and try to close it.

Expected result:
Ticket will be closed without any problem; because ticket1 depends on ticket2 and ticket 2 does not depend on anything.

Actual result:
Ticket cannot be closed and error is printed in the top of page:
**You cannot close a ticket that has ticket depending that are still open. **


BTW I am not a native speaker but IMHO blocked and depends on has the same semantic.
Which is really confusing as I mentioned in title. blocked by would be clear enough that is not a typo. We used custom fields in sssd trac with names: Blocked By: and Blocking: I am not proposing these one but IMHO they are more clear.

Anyway, if label blocked will be changed then the behaviour still does not match with semantic of words in English.

BTW My plan was to set values of attributes depends/blocks in JSONs after importing tickets from sssd trac and get rid of custom fields before import. We already have bunch of custom fields.

Metadata Update from @lslebodn:
- Issue tagged with: IDM

Metadata Update from @pingou:
- Issue assigned to pingou

Commit a8a5f48f fixes this issue

Metadata